Keymap imports unreliable #119408

New Issue

Thespikedballofdoom · 2024-03-13T02:11:41+01:00

2024-03-13 02:11:41 +01:00

System Information
Operating system: Windows 10
Graphics card: Nvidia RTX 3070 Ti

Blender Version
Broken: 4.0.2, 4.1.0 alpha, 3.6.0 to some extent

Exact steps for others to reproduce the error

The following keymap was created on 4.0.2 but only 3.6.0 seems to be able to import the W and D keyframe change keys in the 'Frame' section. I attempted to import it on 4.1.0a and it also dropped those keys.

In addition, editing a keymap after importing it then removing it with the minus - button next to the presets, and reimporting it keeps the changes you made previously when it should be overwritten by the freshly imported map.

**System Information** Operating system: Windows 10 Graphics card: Nvidia RTX 3070 Ti **Blender Version** Broken: 4.0.2, 4.1.0 alpha, 3.6.0 to some extent **Exact steps for others to reproduce the error** The following keymap was created on 4.0.2 but only 3.6.0 seems to be able to import the W and D keyframe change keys in the 'Frame' section. I attempted to import it on 4.1.0a and it also dropped those keys. In addition, editing a keymap after importing it then removing it with the minus - button next to the presets, and reimporting it keeps the changes you made previously when it should be overwritten by the freshly imported map.

Blender keybinds export 20 (4.0.2) [Frames D W - shiftD].py

127 KiB

Thespikedballofdoom added the

labels 2024-03-13 02:11:42 +01:00

Thespikedballofdoom commented

2024-03-13 02:55:45 +01:00

It seems hitting "restore" on every item in the keymap fixed the dropping, restoring what I thought was dropped... I really don't understand the keymap editor. It's so hard to trust it, I feel like I can't just save and load stuff easily

Pratik Borhade commented

2024-03-14 07:13:57 +01:00

Hi, thanks for the report. Key-items with W and D keys are imported in 4.0.
When you import the keymap, did you find these key-items missing from the keymap list or they are just not working in animation editor?

Hi, thanks for the report. Key-items with `W` and `D` keys are imported in 4.0. When you import the keymap, did you find these key-items missing from the keymap list or they are just not working in animation editor?

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2024-03-14 07:14:06 +01:00

Thespikedballofdoom commented

2024-03-14 10:12:53 +01:00

I had found them missing, but it began to work after I hit the "restore" button on that section and re-imported it. The behavior can be re-caused by deleting those or any keys and looking for them after importing a new keymap, and re-fixed in the same way with the restore button.

I assume it's intended, so my understanding is that the keymap has an additional layer of modification I removed by hitting that which I'm not sure what is meant for. It's very unusual to me that importing a preset wouldn't set all the keys it has; I imagined "Restore" was for restoring the keys to blender default or the preset's default but not that importing wouldn't completely override what I did before.
It would be good to make it more obvious that this is how the keymap handles itself.

I had found them missing, but it began to work after I hit the "restore" button on that section and re-imported it. The behavior can be re-caused by deleting those or any keys and looking for them after importing a new keymap, and re-fixed in the same way with the restore button. I assume it's intended, so my understanding is that the keymap has an additional layer of modification I removed by hitting that which I'm not sure what is meant for. It's very unusual to me that importing a preset wouldn't set all the keys it has; I imagined "Restore" was for restoring the keys to blender default or the preset's default but not that importing wouldn't completely override what I did before. It would be good to make it more obvious that this is how the keymap handles itself.

Pratik Borhade commented

2024-03-15 07:57:39 +01:00

but it began to work after I hit the "restore" button on that section and re-imported it...The behavior can be re-caused by deleting those or any keys and looking for them after importing a new keymap, and re-fixed in the same way with the restore button.

Thanks. This is not very clear to me.
Can you share exact steps to reproduce the problem with default settings so we know where the problem is.

File > Defaults > Load Factory Settings (don't close blender after this)
Perform steps to trigger the issue (this info is missing)
Edit > Preferences > Keymap -> import keymap attached in the report (some keymap entries are gone)

Not sure but keymap entries could be removed if it conflicts with existing pair.

> but it began to work after I hit the "restore" button on that section and re-imported it...The behavior can be re-caused by deleting those or any keys and looking for them after importing a new keymap, and re-fixed in the same way with the restore button. Thanks. This is not very clear to me. Can you share exact steps to reproduce the problem with default settings so we know where the problem is. - `File > Defaults > Load Factory Settings` (don't close blender after this) - Perform steps to trigger the issue (this info is missing) - `Edit > Preferences > Keymap` -> import keymap attached in the report (some keymap entries are gone) Not sure but keymap entries could be removed if it conflicts with existing pair.

Thespikedballofdoom commented

2024-03-15 15:02:57 +01:00

Sure, thank you.

File > Defaults > Load factory settings
Preferences > Keymap
Make changes, I tried removing every key in the "window" section and adding 3 blank entries with K L and Y.
Export this as a keymap preset
Hit "Restore" to restore the Window section back to normal keymaps
Import it as a keymap preset and switch to it, there should be no restore buttons visible anywhere in the keymap
Make changes in this keymap preset, I unchecked all of the Screen > Screen editing keys and added a blank R entry.
Switch back to the "Blender" default keymap preset
Changes will have applied to it as well with the same "Restore" button.

This was what makes me think it's intentional as away to allow user customizations to apply on top of imported keymaps, but it also means what you import isn't immediately what you get, and when I saw the restore button I had assumed it restored the section back to the factory 'Blender' preset defaults. That's what makes them feel unreliable, at least as backups which is what I export them for.

I was more expecting an import to override everything which is how most apps handle keybind presets, so I avoided hitting the restore buttons, and when I had accidentally unbinded W and D in the original post, I kept reimporting the same keymap not understanding why they wouldn't come back.
I manually re added them, exported, removed them and then reimported to make sure the export was working, and then those deletions persisted onto the reimport and I thought blender was broken in some way. Especially after those keys did work when importing in blender 3.6, but it was really just because the settings were default on that install.

Sure, thank you. 1. File > Defaults > Load factory settings 2. Preferences > Keymap 3. Make changes, I tried removing every key in the "window" section and adding 3 blank entries with K L and Y. ![image](/attachments/0834ff4d-abff-4a7a-b628-bbbf1dc9cfb7) 4. Export this as a keymap preset 5. Hit "Restore" to restore the Window section back to normal keymaps 6. Import it as a keymap preset and switch to it, there should be no restore buttons visible anywhere in the keymap 7. Make changes in this keymap preset, I unchecked all of the Screen > Screen editing keys and added a blank R entry. ![image](/attachments/a708879d-0394-480d-94e9-6a229821cba3) 8. Switch back to the "Blender" default keymap preset 9. Changes will have applied to it as well with the same "Restore" button. ![image](/attachments/f0e2a948-554e-4a5e-bec2-d2989a6f8dcb) This was what makes me think it's intentional as away to allow user customizations to apply on top of imported keymaps, but it also means what you import isn't immediately what you get, and when I saw the restore button I had assumed it restored the section back to the factory 'Blender' preset defaults. That's what makes them feel unreliable, at least as backups which is what I export them for. I was more expecting an import to override everything which is how most apps handle keybind presets, so I avoided hitting the restore buttons, and when I had accidentally unbinded W and D in the original post, I kept reimporting the same keymap not understanding why they wouldn't come back. I manually re added them, exported, removed them and then reimported to make sure the export was working, and then those deletions persisted onto the reimport and I thought blender was broken in some way. Especially after those keys did work when importing in blender 3.6, but it was really just because the settings were default on that install.

image.png

27 KiB

image.png

109 KiB

image.png

97 KiB

image.png

96 KiB