translate/rotate/scale, for people to bind to shortcut keys.
wm.context_set doesn't work well here since it just toggles each component on/off.
Fixes [#19730] Missing/conflicting keymaps for "Change Manipulator Mode" function
Good defaults for this can be decided on for an updated 2.5 key layout.
Seemed simple but actually turned out to be quite complex.
ND_MODE notifier was being misused, changed to ND_TOOLSETTINGS
Note: Although the fix itself doesn't involve this much, debugging uncovered
that listeners can't rely on notifier->swinid to be correct, since notifiers can
now be added from RNA without a region context.
Texture handling really needs deeper improvement, this fix doesn't really help for
other situations like modifiers, but solves the inconvenient case of sculpting with
no material at least.
Patches by Jonathan Smith (jaydez)
Add a Cursor Center entry in the snap menu (Shift-S) to reset the cursor to 0,0,0. Also rename the view_center operator to view_selected to reflect better what it does (in the code only, description and name were already ok).
Note: AA is still disabled due to AA creating problems for selection tools. If you must, set AA to 2 or 4 in wm_window.c where the GHOST window is created (line 317).
Was only updating the animation system for the render process - if scene render was skipped
(as is the case for comp trees without renderlayer nodes) then the animation system wouldn't
update.
Added in an update here, Aligorith, maybe you'd like to doublecheck.
Fileselect handlers are added to window's modalhandlers, and contain references to
other areas/regions/etc... Still seems a little bit dodgy, but fixes file selectors for now.
Fun bug, took me the better part of the day to track down.
Happens because maximizing swaps spacedata lists between the old area and the newly created maximized area (this one being empty) while ui handlers are still hanging with references to the first area (then trying to access spacedata when handled). And then only if a maximizing operator was run before the UI realign timer event from the previous maximize was handled (fun, I told you).
After discussion with Matt on irc, we decided the best way to deal with that was to remove ui handlers that reference areas of a screen that is no longer used. That solution reflects the fact that the bug is more general that the reproducing steps would lead to believe. There's also absolutely no reason to run UI handlers on invisible areas.
and other operations the nla mapping would be applied to the curves, but not
restored correctly. The unmap function was not the inverse of the map function,
and it's not clear to me it's even possible to make it so due to repeat, so
now the old coordinates are backed up in a list and then restored afterwards.
transforming, due to the evaluation of the object transform without
constraints, and the driver not finding the property.
Constraints are now disabled in a way that should avoid this problem
