Files
test2/source
Joshua Leung 7a87b89a60 Bugfix [#30097] Motion paths range not correct - Part B (Recalculating existing
paths with new ranges)

If an object/bone already had a motion path, it was not possible to recalculate
it over a different frame range without firstly clearing these paths. This was
both a confusing and troublesome workflow, and has since been removed.
2012-05-01 13:10:36 +00:00
..
2011-05-09 08:15:38 +00:00