Answer
In PME 2.1, seeing Press in Blender’s Keymap preferences is expected for PME Hold, Tweak, and Chords hotkeys. The initial press hands the input to PME, which then watches the timing, movement, release, or chord.
Blender’s Keymap preferences show only that first event. Check the hotkey inside PME to see the mode PME will use.
What Blender records for each PME mode
| PME input mode | Blender keymap event |
|---|---|
| Press | Press |
| Hold | Press |
| Tweak | Press |
| Chords | Press |
| Double Click | Double Click |
| Experimental Click | Click |
| Experimental Click Drag | Click Drag |
The last two are experimental PME modes. Unlike Hold, Tweak, and Chords, they register Blender’s matching event directly.
Diagnose an input that behaves incorrectly
- Open the relevant hotkey in PME and confirm its PME mode is Hold, Tweak, or Chords.
- Confirm that the keymap scope matches the editor and mode where you use it.
- Search PME for another menu using the same key, modifiers, and keymap. A competing Press registration can make the result look immediate.
- For Hold or Tweak, review PME’s configured timing or movement thresholds and test with a clearly longer hold or larger drag.
- Test outside active modal tools, which can consume input before the normal keymap handler.
Keep the generated Blender keymap item on Press. Changing it to Release or another event can prevent PME from seeing the initial press and the rest of the gesture.
Also check
- Blender’s Keymap UI shows the event that starts PME; the full Hold, Tweak, or Chords behavior remains configured in PME.
- A correct Hold registration can still fail because of scope, collision, modal handling, or threshold configuration.
- Double Click and the experimental Click modes register their matching Blender events directly, so their entries differ from Hold and Tweak.
Related answers
- Make one PME hotkey work in Object Mode and Edit Mode
- Export Blender keymaps without ghost PME entries
- Use modifier keys inside one PME item