Blender hotkey priority is defined by order but hotkey editor does not allow for order editing #53710

New Issue

Ludvik Koutny · 2018-01-07T18:08:48+01:00

Ludvik Koutny commented

2018-01-07 18:08:48 +01:00

System Information
Windows 10 FCU
GTX1080Ti

Blender Version
2.79

Hi,

I've discovered this shocking design flaw after spending a few hours scratching my head as to why some of the assigned hotkeys does not work. In my case, transform gizmo planar constraint triggered by holding down Shift key has stopped working. It appears that the Blender decides execution priority of a shortcut based on its order in the list, so if you for example remove view3d.manipulator entries in 3D View (Global) category, and then add these very same entries with very same settings at the bottom, then Planar Constraint mode of manipulator gizmo will stop working, because some other action above will have higher priority.

Aside from being nearly impossible for the end user to figure out why this is not working, as there is no implication of this mechanism, what's even more scary is that hotkey editor in Blender does not allow for re-ordering of assigned hotkeys, so if you add a new hotkey entry, it's always added at the bottom, and only way to fix this is to open exported .py key configuration file in a text editor, and manually edit the order there.

**System Information** Windows 10 FCU GTX1080Ti **Blender Version** 2.79 Hi, I've discovered this shocking design flaw after spending a few hours scratching my head as to why some of the assigned hotkeys does not work. In my case, transform gizmo planar constraint triggered by holding down Shift key has stopped working. It appears that the Blender decides execution priority of a shortcut based on its order in the list, so if you for example remove view3d.manipulator entries in 3D View (Global) category, and then add these very same entries with very same settings at the bottom, then Planar Constraint mode of manipulator gizmo will stop working, because some other action above will have higher priority. Aside from being nearly impossible for the end user to figure out why this is not working, as there is no implication of this mechanism, what's even more scary is that hotkey editor in Blender does not allow for re-ordering of assigned hotkeys, so if you add a new hotkey entry, it's always added at the bottom, and only way to fix this is to open exported .py key configuration file in a text editor, and manually edit the order there.

Ludvik Koutny commented

2018-01-07 18:08:48 +01:00

Added subscriber: @Rawalanche

Philipp Oeser commented

2018-01-09 20:17:31 +01:00

Added subscribers: @ideasman42, @lichtwerk

Campbell Barton was assigned by Philipp Oeser

2018-01-09 20:17:31 +01:00

Philipp Oeser commented

2018-01-09 20:17:31 +01:00

Confirmed, this indeed feels a bit weak.
I havent checked the code yet, so it could be a known limitation... @ideasman42 : is this more of a TODO? (adding a reordering feature would be I guess - not sure if this is an easy task)

Confirmed, this indeed feels a bit weak. I havent checked the code yet, so it could be a known limitation... @ideasman42 : is this more of a TODO? (adding a reordering feature would be I guess - not sure if this is an easy task)

Ludvik Koutny commented

2018-01-09 21:29:29 +01:00

Since 2.8 workflow release is supposed to include also reworked key map, I'd suggest some adjustments to to hotkey editor. In relation to this issue, first thing in order would probably be to add something into the user interface that implies hotkey order from top to bottom is relevant to hotkey functionality, because right now, probably almost no one knows about this. Once users are aware that the descending order of hotkeys is relevant to their functionality, they should have some basic UI elements to customize the order.

But in my opinion, the safest and most intuitive way to handle this would be to remove order dependency completely, and instead do not allow mapping of the same hotkey multiple times in the same mode/panel. While this could be a little limiting, it would remove a lot of room for error current hotkey editor suffers from.

Since 2.8 workflow release is supposed to include also reworked key map, I'd suggest some adjustments to to hotkey editor. In relation to this issue, first thing in order would probably be to add something into the user interface that implies hotkey order from top to bottom is relevant to hotkey functionality, because right now, probably almost no one knows about this. Once users are aware that the descending order of hotkeys is relevant to their functionality, they should have some basic UI elements to customize the order. But in my opinion, the safest and most intuitive way to handle this would be to remove order dependency completely, and instead do not allow mapping of the same hotkey multiple times in the same mode/panel. While this could be a little limiting, it would remove a lot of room for error current hotkey editor suffers from.

Campbell Barton commented

2018-01-10 04:19:07 +01:00

Changed status from 'Open' to: 'Archived'

Campbell Barton closed this issue

2018-01-10 04:19:07 +01:00

Campbell Barton commented

2018-01-10 04:19:07 +01:00

This is a TODO which can be handled with general improvements to the keymap editor.

Added to wiki: https://wiki.blender.org/index.php/Dev:Source/Development/Todo/UserInterface#Keymap_Editing

This is a TODO which can be handled with general improvements to the keymap editor. Added to wiki: https://wiki.blender.org/index.php/Dev:Source/Development/Todo/UserInterface#Keymap_Editing

CybranM commented

2021-06-23 10:12:57 +02:00

Added subscriber: @IihT2cWA9xiP30BsYphz3EiEISNoScoe

CybranM commented

2021-06-23 10:12:57 +02:00

This issue still remains, makes for hotkey editing a lot more annoying

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Blender hotkey priority is defined by order but hotkey editor does not allow for order editing #53710