Bugfixes for Motion Path drawing/updating in light of the recent changes:

* Added proper "update" operators in place of the abuse of the calculate
operators, so now the display ranges won't get overwritten everytime (with the
default values) you go to update the paths.

* Display range settings in properties editor now actually work. Before, the "In
Range" mode only displayed the entire paths.
This commit is contained in:
2012-05-06 04:18:13 +00:00
parent 7c58e6a9f2
commit 5d02292d3c
8 changed files with 107 additions and 23 deletions

View File

@@ -65,12 +65,10 @@ class MotionPathButtonsPanel():
sub.prop(mpath, "frame_start", text="From")
sub.prop(mpath, "frame_end", text="To")
sub = col.column() # align=True
sub.operator_context = 'EXEC_DEFAULT'
if bones:
col.operator("pose.paths_calculate", text="Update", icon='BONE_DATA')
col.operator("pose.paths_update", text="Update Paths", icon='BONE_DATA')
else:
col.operator("object.paths_calculate", text="Update", icon='OBJECT_DATA')
col.operator("object.paths_update", text="Update Paths", icon='OBJECT_DATA')
else:
col.label(text="Not available yet...", icon='ERROR')
col.label(text="Calculate Paths first", icon='INFO')