Keymap: custom key modifiers work inconsistently #68621

New Issue

Jean Ayer · 2019-08-13T19:59:50+02:00

Jean Ayer commented

2019-08-13 19:59:50 +02:00

System Information
Operating system: Arch Linux, no DE, i3wm
Graphics card: GTX 960

Blender Version
Broken: 2.80
Worked: 2.79

Short description of error
I'm left-handed on the tablet, so I bind my sculpt hotkeys to the numberpad. Binding NumpadEnter+LMB to sculpt inverted (same as holding Ctrl) no longer works in 2.80. However, binding NumpadEnter+MMB to pan the view does work. Not sure where the conflict is. This setup did work in Blender 2.79.

Exact steps for others to reproduce the error
Load factory settings
Import .py keymap provided (or bind manually; sculpt.brush_stroke and view3d.move)
Enter sculpt mode
Attempt to sculpt inverted by holding NumpadEnter+LMB

system-info.txt
custom_modifier_bug.py

Similar bugs from ages ago:
https://developer.blender.org/T44349
https://developer.blender.org/T34822

**System Information** Operating system: Arch Linux, no DE, i3wm Graphics card: GTX 960 **Blender Version** Broken: 2.80 Worked: 2.79 **Short description of error** I'm left-handed on the tablet, so I bind my sculpt hotkeys to the numberpad. Binding NumpadEnter+LMB to sculpt inverted (same as holding Ctrl) no longer works in 2.80. However, binding NumpadEnter+MMB to pan the view does work. Not sure where the conflict is. This setup did work in Blender 2.79. **Exact steps for others to reproduce the error** Load factory settings Import .py keymap provided (or bind manually; sculpt.brush_stroke and view3d.move) Enter sculpt mode Attempt to sculpt inverted by holding NumpadEnter+LMB [system-info.txt](https://archive.blender.org/developer/F7662809/system-info.txt) [custom_modifier_bug.py](https://archive.blender.org/developer/F7662810/custom_modifier_bug.py) Similar bugs from ages ago: https://developer.blender.org/T44349 https://developer.blender.org/T34822

Jean Ayer commented

2019-08-13 19:59:50 +02:00

Added subscriber: @vravCodyBurrow

blender-admin commented

2019-08-13 19:59:50 +02:00

#103191 was marked as duplicate of this issue

blender-admin commented

2019-08-13 19:59:50 +02:00

#85042 was marked as duplicate of this issue

blender-admin commented

2019-08-13 19:59:50 +02:00

#78258 was marked as duplicate of this issue

blender-admin commented

2019-08-13 19:59:50 +02:00

#67929 was marked as duplicate of this issue

CJ Ferguson commented

2019-11-08 15:41:53 +01:00

Added subscriber: @CJ-Ferguson

CJ Ferguson commented

2019-11-08 15:41:53 +01:00

I also have issues with custom modifier keys. Namely "spacebar". For instance if I have a hotkey assigned to "spacebar R". This doesn't work unless I have deactivated any hotkey that is using "R". The software doesn't register that "spacebar" is putting existing keys into a different modified state.

Offtopic
Another weird quirk is that "shift Right Mouse (view3d.cursor3d)" cannot be reassigned to any other hotkey and maintain its drag function. For instance if I assign view3d.cursor3d to "alt right mouse" I am unable to use the drag cursor functionality. Somewhat strangely, if you disable "shift right mouse for view3d.cursor3d" the hotkey still works no matter what. It's like the blender thinks this hotkey is so essential that there is no way to dispose of it or change it to something else.

I would love if the hotkey editor were completely transparent and didn't hide functionality from the user as I keep running into conflicts where blender acts like it can be completely customizable, but behind the scenes it's holding back.

I also have issues with custom modifier keys. Namely "spacebar". For instance if I have a hotkey assigned to "spacebar R". This doesn't work unless I have deactivated any hotkey that is using "R". The software doesn't register that "spacebar" is putting existing keys into a different modified state. **Offtopic** Another weird quirk is that "shift Right Mouse (view3d.cursor3d)" cannot be reassigned to any other hotkey and maintain its drag function. For instance if I assign view3d.cursor3d to "alt right mouse" I am unable to use the drag cursor functionality. Somewhat strangely, if you disable "shift right mouse for view3d.cursor3d" the hotkey still works no matter what. It's like the blender thinks this hotkey is so essential that there is no way to dispose of it or change it to something else. I would love if the hotkey editor were completely transparent and didn't hide functionality from the user as I keep running into conflicts where blender acts like it can be completely customizable, but behind the scenes it's holding back.

Germano Cavalcante commented

2019-12-26 16:49:58 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2019-12-26 16:49:58 +01:00

That's strange, but it seems that is designed to work like this. See:
https://developer.blender.org/diffusion/B/browse/master/source/blender/windowmanager/intern/wm_event_system.c$2050-2052

  /* Only keymap entry with keymodifier is checked,
   * means all keys without modifier get handled too. */
  /* That is currently needed to make overlapping events work (when you press A - G fast or so). */

keymodifiers other than Ctrl, Shift, Alt, OSkey are not checked by keymaps without keymodifiers.
This causes the first keymap in the list (which in this case is the one with Left Mouse and without the Numpad Enter modifier) to be used.

A workaround is to move the keymap without the modifier to the bottom of the list (by deleting the keymap that has only Left Mouse and creating it again).

That's strange, but it seems that is designed to work like this. See: https://developer.blender.org/diffusion/B/browse/master/source/blender/windowmanager/intern/wm_event_system.c$2050-2052 ``` /* Only keymap entry with keymodifier is checked, * means all keys without modifier get handled too. */ /* That is currently needed to make overlapping events work (when you press A - G fast or so). */ ``` keymodifiers other than `Ctrl, Shift, Alt, OSkey` are not checked by keymaps without keymodifiers. This causes the first keymap in the list (which in this case is the one with `Left Mouse` and without the `Numpad Enter` modifier) to be used. A workaround is to move the keymap without the modifier to the bottom of the list (by deleting the keymap that has only `Left Mouse` and creating it again).

Germano Cavalcante commented

2020-01-03 14:51:43 +01:00

Added subscriber: @peroro

CJ Ferguson commented

2020-01-06 17:55:31 +01:00

Thank you! This information was extremely helpful as I was mourning the loss of my spacebar modifier and though I think hotkey setup in blender should use modo as a template (including an easily comprehendable text file that you can edit hotkeys in) I'm happy to find that part of blender's lack of functionality was just my own lack of knowledge of how its hotkeys work.

Germano Cavalcante commented

2020-01-07 17:46:12 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Germano Cavalcante commented

2020-06-25 23:05:43 +02:00

Added subscriber: @Genomo

Germano Cavalcante commented

2021-01-26 15:56:06 +01:00

Added subscriber: @Neigh

Nathan Clark commented

2021-02-27 18:07:11 +01:00

In #68621#837961, @mano-wii wrote:
A workaround is to move the keymap without the modifier to the bottom of the list (by deleting the keymap that has only Left Mouse and creating it again).

Hi Germano, hoping you might go into a bit more detail here? My confusion is such: If I create the following keymap Window > New File and I set it to F19 A then this will also trigger the "select all" command. But I can't put the new keymap above Object Mode > (De)select All because they are in separate branches of the keymap tree. Can you help make sense of how to implement the workaround? (is it even possible?)

> In #68621#837961, @mano-wii wrote: > A workaround is to move the keymap without the modifier to the bottom of the list (by deleting the keymap that has only `Left Mouse` and creating it again). Hi Germano, hoping you might go into a bit more detail here? My confusion is such: If I create the following keymap `Window > New File` and I set it to `F19 A` then this will also trigger the "select all" command. But I can't put the new keymap above `Object Mode > (De)select All` because they are in separate branches of the keymap tree. Can you help make sense of how to implement the workaround? (is it even possible?)

Germano Cavalcante commented

2022-12-14 18:07:06 +01:00

Added subscriber: @Rays-Lv

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Keymap: custom key modifiers work inconsistently #68621