Remapping Dynamic Context Menu Key changes binding in all KeyConfig presets #52938

Closed
opened 2017-09-28 20:26:01 +02:00 by A.H. Doornbos · 7 comments

System Information
Windows 10 AMD HD5850

Blender Version
Broken: 2.78 (and likely before)
Worked: (optional)

Short description of error
Rebinding the key for dynamic context menu ("spacebar" by default) changes binding in all KeyConfig presets. So if I create a new KeyConfig preset and change the binding to for example "action mouse" the blender default, 3DS max and Maya and any other KeyConfig changes as well.

Exact steps for others to reproduce the error
No .blend file needed. Go to User Preferences>Addons and activate Dynamic Context Menu. Next go to Input and navigate to the 3D View>3D View (Global) Section and find the "call menu" entry that belongs to Dynamic Context Menu (should be the first). Change the binding to anything other than "spacebar". Now change the KeyConfig preset to something else. Note that the binding has also changed there. Now restore the binding to default and switch back to the previous KeyConfig preset and notice that your binding has been reset there too.

The Dynamic Context Menu although an "oldie" is still a usefull addon, but so is search. It would be nice if you could use it under a different key binding, but if this possibly disrupts other existing keymapping configurations this can be an issue.

**System Information** Windows 10 AMD HD5850 **Blender Version** Broken: 2.78 (and likely before) Worked: (optional) **Short description of error** Rebinding the key for dynamic context menu ("spacebar" by default) changes binding in all KeyConfig presets. So if I create a new KeyConfig preset and change the binding to for example "action mouse" the blender default, 3DS max and Maya and any other KeyConfig changes as well. **Exact steps for others to reproduce the error** No .blend file needed. Go to User Preferences>Addons and activate Dynamic Context Menu. Next go to Input and navigate to the 3D View>3D View (Global) Section and find the "call menu" entry that belongs to Dynamic Context Menu (should be the first). Change the binding to anything other than "spacebar". Now change the KeyConfig preset to something else. Note that the binding has also changed there. Now restore the binding to default and switch back to the previous KeyConfig preset and notice that your binding has been reset there too. The Dynamic Context Menu although an "oldie" is still a usefull addon, but so is search. It would be nice if you could use it under a different key binding, but if this possibly disrupts other existing keymapping configurations this can be an issue.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @roujin.x

Added subscriber: @roujin.x
Member

Added subscriber: @BrendonMurphy

Added subscriber: @BrendonMurphy
Member

hi, this is not a bug, if you have the addon active and change it's keybinding it's expected that the keybinding is globally accepted across keymaps.
I would expect any or all addons to do this.
closing as invalid

hi, this is not a bug, if you have the addon active and change it's keybinding it's expected that the keybinding is globally accepted across keymaps. I would expect any or all addons to do this. closing as invalid
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brendon Murphy self-assigned this 2017-09-29 11:19:35 +02:00

Added subscriber: @VukGardasevic

Added subscriber: @VukGardasevic

Like @BrendonMurphy said, that is related to how add-on/user script shortcuts get registered/handled in general and not only to Dynamic Context Menu.

In the future with establishing the Blender Templates (101 project) and reworking of the shortcuts system that could possibly be changed.

For now You can go around it several ways.

  1. The Search is included on top in the Dynamic menu > regular clicking (too slow sometimes)
  2. Look at the little underline in the Search entry - it should be under a letter (in 2.77, 2.78 and 2.79 is S) so Press Spacebar + S and start typing for the operator.
  3. First 9 entries in menu can be accessed with number keys. Since Search is first you can Press Spacebar + 1
  4. Edit the script default in python. To check what keys are not used the Is Key Free can be helpful (add-on is shipped with 2.79).
Like @BrendonMurphy said, that is related to how add-on/user script shortcuts get registered/handled in general and not only to Dynamic Context Menu. In the future with establishing the Blender Templates (101 project) and reworking of the shortcuts system that could possibly be changed. For now You can go around it several ways. 1) The Search is included on top in the Dynamic menu > regular clicking (too slow sometimes) 2) Look at the little underline in the Search entry - it should be under a letter (in 2.77, 2.78 and 2.79 is S) so Press `Spacebar + S` and start typing for the operator. 3) First 9 entries in menu can be accessed with number keys. Since Search is first you can Press `Spacebar + 1` 4) Edit the script default in python. To check what keys are not used the Is Key Free can be helpful (add-on is shipped with 2.79).
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-addons#52938
No description provided.