Page MenuHome

Pie Menu: 3D Viewport Pie Menus keep making new keybinds when activating them
Closed, ResolvedPublic

Description

System Information
Operating system: Windows 10 and 7 (two computers)
Graphics card: Geforce GTX 980 and 1060 respectively.

Blender Version
Broken: 2.80, hash: 96f762500ef9, 2019-01-07 00:16

Short description of error
Was working on my custom keybinds and I wanted to add the pie menus into my workflow. However, because some of them are add-ons, they automatically added the old keybinds into my settings, which messed up a bunch of my keys from working like they should (i.e. the tool menu I hotkeyed to Q stopped working and was instead showing the view numpad pie: hotkey Q add-on)

Exact steps for others to reproduce the error

  1. Download the keybindings file (check the pdf for my current documentation for extra info about my changes, since I am still working on them quite extensively) and install them.
  2. Try using the keybindings for the add-on menus I made before activating the add-on.
  3. Activate the add-on Pie Menu: 3D Viewport Pie Menus and check on the pie menus (the pdf provides information about the keybinds on page 1).
  4. Check the input/keymap tab in preferences. You will see a bunch of new menu shortcuts being added to various places (the final page of the pdf goes into more detail)

The only solution I have found is to manually remove the keybinds that the add-on automatically adds, but it is a very tedious process that I have to repeat every time I download and install a new, clean version of Blender. I would prefer if you could just deactivate automatic add-on keybinds with a button so you don't have to remove them yourself.


Details

Type
Bug

Event Timeline

hi, Addons are specifically designed to interfere as little as possible with Blender default keymaps. They are also iirc, loaded at start up. You are using custom keymaps which can fall outside the scope of addons design and default key mappings at the moment. I feel that what you are requesting is outside of addons/keymap current design. To get around this you can edit the individual files that give you trouble with your custom keymap. I'm not sure this is a bug or a feature request or simply a limitation of the current design and the way things work.
A more knowledgeable blender developer may correct me if I'm wrong here.

hi, Addons are specifically designed to interfere as little as possible with Blender default keymaps. They are also iirc, loaded at start up. You are using custom keymaps which can fall outside the scope of addons design and default key mappings at the moment. I feel that what you are requesting is outside of addons/keymap current design. To get around this you can edit the individual files that give you trouble with your custom keymap. I'm not sure this is a bug or a feature request or simply a limitation of the current design and the way things work.
A more knowledgeable blender developer may correct me if I'm wrong here.

Seems like more of a fairly big oversight to design automatic keybinds without an easy way to change/remove them when it is fully within reason for a user to want to change keybinds if they so desire, even in the older versions of Blender. Besides, the 2.8 beta is already in the middle of changing the keybinds and menus to accommodate users from other 3D software by adding L click select as a default option and more, so I disagree that it is outside of the current design, especially when said design is constantly changing. Also, I have been changing them manually, which is why this thread exists to begin with, to possibly get a proper fix to the problem. As for it being a bug or a feature, my guess is that it was intentionally designed that way, but it is a feature with consequences and is making a problem.

hi, e66bf5191ff2 should fix this issue. I've checked that the addons keymaps are removed correctly. In the end I was able to reproduce your issue with load factory settings giving an error.

hi, e66bf5191ff2 should fix this issue. I've checked that the addons keymaps are removed correctly. In the end I was able to reproduce your issue with load factory settings giving an error.

Thanks for taking a look at the issue! I truly appreciate it! :)