make transform modal map 'Orientation XXX axis' constraints more consistent with default ('X'/'Y'/'Z') behaviour #42354

New Issue

Philipp Oeser · 2014-10-22T21:23:11+02:00

Philipp Oeser commented

2014-10-22 21:23:11 +02:00

Hi there,

I was recently approached by a former colleague [Softimage convert:)] to see if I could enable the following behaviour:

let's say the user configures shortcuts for 'Orientation X axis', 'Orientation Y axis' or 'Orientation Y axis' in 'Transform Modal Map'.
The behaviour then differs between these custom shortcuts and the default/hardcoded 'X', 'Y' and 'Z' keyboard keys.

This is what happens when the user has no shortcuts set:

enter transform (usually 'g')
press 'X' the first time: constraint to global X axis
press 'X' the second time: constraint to local (or better: whatever is currently set in SpaceView3D.transform_orientation) X axis
press 'X' the third time: constraint OFF
so it cycles through these three... (which can be very convenient)
[codewise this is handled by 'transform_event_xyz_constraint()' in transform.c]

This is what happens when the user has shortcuts set (see pic below):

enter transform (usually 'g')
press 'shortcut for X' the first time: global (or better: whatever is currently set in SpaceView3D.transform_orientation) X axis
press 'shortcut for X' the third time: constraint OFF
so it just toggles between these two... (no chance to quickly toggle between e.g. global/local)
[codewise this is handled more or less by calling 'setUserConstraint()' directly]

Well, the following little patch makes this more 'consistent' by also calling transform_event_xyz_constraint() in the case of the modal keymap.
(getting the exact same as the default ('X'/'Y'/'Z') behaviour)
TransformConstraintModalMapTweak.patch

Let me know what you think...

Hi there, I was recently approached by a former colleague [Softimage convert:)] to see if I could enable the following behaviour: let's say the user configures shortcuts for 'Orientation X axis', 'Orientation Y axis' or 'Orientation Y axis' in 'Transform Modal Map'. The behaviour then differs between these custom shortcuts and the default/hardcoded 'X', 'Y' and 'Z' keyboard keys. **This is what happens when the user has no shortcuts set:** - enter transform (usually 'g') - press 'X' the first time: constraint to _global_ X axis - press 'X' the second time: constraint to _local_ (or better: whatever is currently set in SpaceView3D.transform_orientation) X axis - press 'X' the third time: constraint OFF so it cycles through these three... (which can be very convenient) [codewise this is handled by 'transform_event_xyz_constraint()' in transform.c] **This is what happens when the user _has_ shortcuts set (see pic below):** - enter transform (usually 'g') - press 'shortcut for X' the first time: global (or better: whatever is currently set in SpaceView3D.transform_orientation) X axis - press 'shortcut for X' the third time: constraint OFF so it just toggles between these two... (no chance to quickly toggle between e.g. global/local) [codewise this is handled more or less by calling 'setUserConstraint()' directly] ![TransformConstraintModalMapTweak.png](https://archive.blender.org/developer/F119224/TransformConstraintModalMapTweak.png) Well, the following little patch makes this more 'consistent' by also calling transform_event_xyz_constraint() in the case of the modal keymap. (getting the exact same as the default ('X'/'Y'/'Z') behaviour) [TransformConstraintModalMapTweak.patch](https://archive.blender.org/developer/F119226/TransformConstraintModalMapTweak.patch) Let me know what you think...

Philipp Oeser commented

2014-10-22 21:23:11 +02:00

Changed status to: 'Open'