When customizing keymaps its useful to use keys which won’t conflict with Blender’s default keymap.
Here are keys which aren’t used and aren’t likely to be used in the future.
- F-Keys (F5 - F8)
These F-Keys (including modifier combination) have been intentionally kept free for users to bind their own keys to.
- OS-Key (also known as the
Blender doesn’t use this key for any bindings.
macOS is an exception, where a few macOS shortcuts are bound to Cmd (cut/copy/paste/preferences).
- Modifier Double Click
Binding modifier keys as primary keys is supported, to avoid conflicts with regular usage you can bind them to double click.
It’s possible to configure a single key to perform multiple operations using Click event instead of Press, Then you may bind Drag to a separate action.
This is useful for mixing actions where one uses a drag event, e.g: Toggle a setting using with tab, drag to open a pie menu showing all options related to the setting.
Unlike click/drag, this only works for the mouse buttons, but has the advantage that tweak events can be directional.
To use this, events in this key-map must use Click instead of Press, then you can bind Tweak actions to the mouse buttons.
This is used in the default key-map in the 3D Viewport, Alt-MMB dragging in different directions rotates the view.
This section lists useful generic operations which can be used.
Key Bindings for Pop-Ups¶
Menus and panels can be assigned key shortcuts, even if they’re only accessible from sub-menus elsewhere.
- Open a Pop-up Menu (
Open any menu on key press.
- Open a Pie Menu (
Open any pie menu on key press.
- Open a Panel (
Open a pop-up panel (also known as a pop-over).
Currently there is no way to find a panel identifier,
besides looking into the Python source code, search for the panel title,
the identifier will use the convention
Key Bindings for Properties¶
There are many properties you might want to bind a keys with. To avoid having to define operators for each property, there are generic operators for this purpose:
Operators for adjusting properties begin with
Some of these include:
wm.context_toggletoggle a boolean property.
wm.context_cycle_enumcycle an enum property forwards or backwards.
wm.context_menu_enumshow a pop-up menu for an enum property.
wm.context_pie_enumshow a pie menu for an enum property.
wm.context_scale_floatscale a number (use for increasing / decreasing brush size for example).
wm.context_toggle_enumtoggle between two options of an enum.
wm.context_modal_mousemoving the cursor to interactively change a value.
See bpy.ops.wm for a complete list.
Each of these operators has a
data_path setting to reference the property to change.
To find the
data_path basic Python knowledge is needed.
For example, you can use the Python Console to access a boolean property you wish to map to a key:
To bind this to a key, add a new keymap item using the operator
data_path set to
object.show_name (notice the
bpy.context prefix is implicit).
See bpy.context for other context attributes.
The Python API documentation can be used to find properties or you may use the Python Console’s auto-complete to inspect available properties.