Page MenuHome

Some bugs on Create Orientation operator
Closed, DuplicatePublic


System Information
win8.1 64bit | GTX680

Blender Version
Broken: 2.69 - 2.75a (so far)

Short description of error
I think there are some very strange behavior on the Create Orienation operator, though different between Object and Edit mode.

Exact steps for others to reproduce the error

  • Problem in Object Mode:

Select an object, then click the "+" button on Transform Orientation panel located in N sidebar. when uncheck the "Use after creation" button in F6 panel, the new created one is still used.

  • Problems in Edit Mode:
  1. Same as above.
  1. Select a element then click the "+" button on Transform Orientation panel. Then try to name it, then rename it. you will see the renaming work will cause a duplication. What's more worse is that toggling any of the other three buttons below will also duplicate the existing one, and rename it like *.001,, *.002....

Btw... perhaps it would be better to capitalize the "Use after creation" as "Use After Creation", and "Overwrite previous" as "Overwrite Previous"? (not critical though...)

Thanks for checking.

Event Timeline

Leon Cheung (leon_cheung) raised the priority of this task from to 90.
Leon Cheung (leon_cheung) updated the task description. (Show Details)
Leon Cheung (leon_cheung) edited a custom field.
Bastien Montagne (mont29) lowered the priority of this task from 90 to Normal.Sep 4 2015, 9:48 AM

All those issues have the same root - undo/redo stack vs. UI.

Typically, when doing undo/redo, we do not alter UI/tools settings, since those are not data. Here it seems transform spaces themselves are handled in 'Globla undo' stack, but not by the Edit mode stack - and the selected TS (which is 3DView editor setting) is totally ignored by undo…

Think this is more known limitation/TODO than really a bug, @Campbell Barton (campbellbarton), @Sergey Sharybin (sergey)?

This is definitively not easily fixable, it’s yet another weakness of our undo stack, and will need some re-design to be addressed. Thanks for the report, closing it for now (added a TODO note about it - we already had quite a similar report actually, see T42468).