Keymap corruption - Adjustments to one keymap propagate to another #94606

New Issue

Hologram · 2022-01-03T16:32:08+01:00

Hologram commented

2022-01-03 16:32:08 +01:00

System Information
Operating system: Windows 10
Graphics card: Nvidia GTX 1070

Blender Version
Broken: 2.83-3.0

Short description of error
Over the course of two years that I have been using Blender on and off, I kept running into an issue where my custom hotkeys were removed from my keymap. This happened with hotkeys that I had been working with for months that worked perfectly fine (even just an hour ago at times). I have had dozens of instances where my custom hotkeys (but also those from the default keymap) were removed entirely without any other notable changes by me. Sometimes, they reverted back to the "factory reset" state, while I did not perform a factory reset. This is only for a few hotkeys at a time.

When creating a keymap entry within a custom keymap, these entries are propagated back to the default "Blender" and "Industry Compatible" keymaps. When switching keymaps, other hotkeys custom hotkeys are assigned to the other keymaps or default keymap items become associated to the custom keymap. It occored for instance, after checking for new hotkeys within the default keymaps (i.e. the 3.0 knife tool modal hotkeys).

Exact steps for others to reproduce the error

Go to Edit > preferences
Create a new keymap with the "+" button.
Right click preferences > Create keyboard shortcut
Type in "Ctrl+K"
Go back to Edit> preferences
When switching keymaps from the dropdown, notice that any of the assigned hotkeys in the custom keymap also exist within the default Blender & Industry compatible keymaps.

Keymap corruption - not saved.mp4

Upon saving preferences for the custom keymap, the default ones remain affected.

2022-01-03 16-14-36.mp4

I suspect that, when switching keymaps (e.g. to check the default modal hotkeys for the new 3.0 Knife tool), default keys are put back into the custom keymap, thereby reverting some of the entries within a custom keymap. This is the reverse behaviour displayed in the videos above. Just like switching from the custom keymap to the default, adds custom keymaps to the default keymaps.

Expectation
I would expect that changing the keymap from the dropdown would load the other keymap and drop the changes made to the custom keymap (and prompt the user with a warning to save the current adjustments or to discard them). That way, if I migrate from a previous Blender version to the next, whilst retaining my custom keymap, I can look at the Blender/ Industry standard keymaps of the new version, which have all the new operators and modal keys assigned. That way, I would be able to copy/ paste them into my custom keymap and make sure it is up to date. Furthermore, I don't expect changes made to my own keymap to override the default Blender/ Industry standard, since the adjustments I made were made to my own custom keymap.

**System Information** Operating system: Windows 10 Graphics card: Nvidia GTX 1070 **Blender Version** Broken: 2.83-3.0 **Short description of error** Over the course of two years that I have been using Blender on and off, I kept running into an issue where my custom hotkeys were removed from my keymap. This happened with hotkeys that I had been working with for months that worked perfectly fine (even just an hour ago at times). I have had dozens of instances where my custom hotkeys (but also those from the default keymap) were removed entirely without any other notable changes by me. Sometimes, they reverted back to the "factory reset" state, while I did not perform a factory reset. This is only for a few hotkeys at a time. When creating a keymap entry within a custom keymap, these entries are propagated back to the default "Blender" and "Industry Compatible" keymaps. When switching keymaps, other hotkeys custom hotkeys are assigned to the other keymaps or default keymap items become associated to the custom keymap. It occored for instance, after checking for new hotkeys within the default keymaps (i.e. the 3.0 knife tool modal hotkeys). **Exact steps for others to reproduce the error** 1. Go to Edit > preferences 2. Create a new keymap with the "+" button. 3. Right click preferences > Create keyboard shortcut 4. Type in "Ctrl+K" 5. Go back to Edit> preferences 6. When switching keymaps from the dropdown, notice that any of the assigned hotkeys in the custom keymap also exist within the default Blender & Industry compatible keymaps. [Keymap corruption - not saved.mp4](https://archive.blender.org/developer/F12786855/Keymap_corruption_-_not_saved.mp4) 7. Upon saving preferences for the custom keymap, the default ones remain affected. [2022-01-03 16-14-36.mp4](https://archive.blender.org/developer/F12786871/2022-01-03_16-14-36.mp4) I suspect that, when switching keymaps (e.g. to check the default modal hotkeys for the new 3.0 Knife tool), default keys are put back into the custom keymap, thereby reverting some of the entries within a custom keymap. This is the reverse behaviour displayed in the videos above. Just like switching from the custom keymap to the default, adds custom keymaps to the default keymaps. **Expectation** I would expect that changing the keymap from the dropdown would load the other keymap and drop the changes made to the custom keymap (and prompt the user with a warning to save the current adjustments or to discard them). That way, if I migrate from a previous Blender version to the next, whilst retaining my custom keymap, I can look at the Blender/ Industry standard keymaps of the new version, which have all the new operators and modal keys assigned. That way, I would be able to copy/ paste them into my custom keymap and make sure it is up to date. Furthermore, I don't expect changes made to my own keymap to override the default Blender/ Industry standard, since the adjustments I made were made to my own custom keymap.

Hologram commented

2022-01-03 16:32:08 +01:00

Added subscriber: @Hologram

Hologram changed title from ~~Keymap corruption - keymap entries are arbitrarily removed from my custom keymap~~ to Keymap corruption - Adjustments to one keymap propagate to another

2022-01-03 23:03:47 +01:00

Pratik Borhade commented

2022-01-04 10:12:32 +01:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2022-01-04 10:37:10 +01:00

Hi, thanks for the report. Can confirm. Same issue has been reported already (#86228) so I will have to close this one.

Pratik Borhade commented

2022-01-04 10:42:32 +01:00

Closed as duplicate of #86228

Pratik Borhade closed this issue

2022-01-04 10:42:32 +01:00

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

Keymap corruption - Adjustments to one keymap propagate to another #94606