Post #5516: I’m not deeply familiar with keymap issues since I rarely encounter them myself.
📋 Metadata
- Author: Pluglug
- Date: 2025-07-06 02:45:43
- Type:
answer - Quality Score: 8/10
- Reply to: post_05511
- Replies (1): post_05517
🏷️ Tags
hotkeys conflicts advanced unsolved
⚙️ Related PME Features
- Hotkey Configuration
- Pie Menu Editor
💬 Content
I’m not deeply familiar with keymap issues since I rarely encounter them myself. I’ve had similar strange situations using Blender’s native export/import tools, and the 4.1 to 4.2 transition was also troublesome.
Is there at least a way to prevent this from happening again?
The simplest approach is starting from a completely clean environment without inheriting any previous preferences.
Technical background: When PME registers/removes keymaps, it relies on identifying KeyMapItems through combinations of idname and properties. However, when ghost keys with null/empty properties appear (like in your case), PME can’t recognize them for proper cleanup. Blender 4.5 introduced new keymap utility methods like find_match() that could solve this, but integrating them into PME would take considerable time.
Since I can’t reproduce this ghost keymap issue myself, would you mind documenting the exact steps that trigger it? A reliable reproduction scenario would be valuable for the community.
Something like:
- Fresh Blender 4.4 install
- Install PME version X.X
- Create pie menu with specific settings
- Remove/disable the menu using [method]
- Ghost keys appear after [trigger event]
If you can nail down the reproduction steps, sharing them here would help others avoid the issue and potentially lead to a proper fix.
❤️ 1 likes