Outcome
Keep one editable Pie Menu but open it from a second shortcut. The additional shortcut belongs to a one-command Stack Key that calls the original menu:
open_menu("Transform")Replace Transform with the exact name of your target menu.
Steps
-
Build and test the target Pie Menu with its primary hotkey.
-
Create a Stack Key named after the additional trigger, such as
Open Transform — Q. -
Keep one Command item and enter:
open_menu("Transform") -
Assign the Stack Key’s hotkey and keymap context.
-
Leave Stack Key options such as Remember Slot off for this one-command wrapper.
-
Test both triggers in their intended Blender editors and modes.
The menu content remains in one place. Editing Transform changes what both shortcuts open.
When the same key should open different menus
Blender keymaps are contextual. The same physical key can lead to different PME menus in different compatible keymap contexts—for example, one in Object Mode and another in Mesh Edit Mode. Keep those contexts explicit, test each one, and give bindings in the same keymap distinguishable conditions.
For more complex decisions inside one trigger, use a context-specific menu route instead of multiplying wrappers.
Pitfalls
open_menu()uses the target’s name. If you rename the target menu, update each wrapper command.- A wrapper creates another Blender keymap entry, so keymap priority and conflicts still apply.
- Point every wrapper at the same Pie Menu so its contents stay synchronized.
- Leave Stack Key cycling options disabled for a single wrapper command.
- When reusing the menu inside another PME menu rather than from a keyboard shortcut, add a Menu item instead. That creates a managed link and is easier to navigate while editing.
Related answers
- Make one hotkey work in Object and Edit Mode
- Resolve hotkey conflicts
- Route one trigger to the current context