sandey/blender
1
0
Fork 0
forked from bartvdbraak/blender
Code Pull Requests Activity

Another attempt to reduce the confusion between Object and Bone constraints

Browse Source 
* The wording on the "Add Constraint" dropdown has been changed so that there is
no ambiguitiy about which tab is currently selected. That is, it now mentions
whether these are object or bone constraints, so that users don't need to try
and look up at the header to check.

* Show the warning about Ob vs Bone constraints when in armature editmode too.
This commit is contained in:
Joshua Leung 2013-03-11 01:53:21 +00:00
parent 722ada58fc
commit 1428f0ebdb
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
release/scripts/startup/bl_ui/properties_object_constraint.py
View File

@ -853,12 +853,12 @@ class OBJECT_PT_constraints(ConstraintButtonsPanel, Panel):
ob = context.object
if ob.mode == 'POSE':
if ob.type == 'ARMATURE' and ob.mode in ('EDIT', 'POSE'):
box = layout.box()
box.alert = True
box.label(icon='INFO', text="See Bone Constraints tab to Add Constraints to active bone")
else:
layout.operator_menu_enum("object.constraint_add", "type")
layout.operator_menu_enum("object.constraint_add", "type", text="Add Object Constraint")
for con in ob.constraints:
self.draw_constraint(context, con)
@ -876,7 +876,7 @@ class BONE_PT_constraints(ConstraintButtonsPanel, Panel):
def draw(self, context):
layout = self.layout
layout.operator_menu_enum("pose.constraint_add", "type")
layout.operator_menu_enum("pose.constraint_add", "type", text="Add Bone Constraint")
for con in context.pose_bone.constraints:
self.draw_constraint(context, con)