Another attempt to reduce the confusion between Object and Bone constraints
authorJoshua Leung <aligorith@gmail.com>
Mon, 11 Mar 2013 01:53:21 +0000 (01:53 +0000)
committerJoshua Leung <aligorith@gmail.com>
Mon, 11 Mar 2013 01:53:21 +0000 (01:53 +0000)
* 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.

release/scripts/startup/bl_ui/properties_object_constraint.py

index f1bad22..0dfb307 100644 (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)