Maniphest T68363

Custom keymap with shortcut for ic_keymap.mesh_select_mode doesn't work after restarting Blender
Closed, Duplicate

Assigned To
Campbell Barton (campbellbarton)
Authored By
Robert Guetzkow (rjg)
Aug 7 2019, 2:21 PM
Tags
  • BF Blender
Subscribers
Campbell Barton (campbellbarton)
Robert Guetzkow (rjg)
William Reynish (billreynish)

Description

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 416.34

Blender Version
Broken: version: 2.81 (sub 1), branch: master, commit date: 2019-08-04 08:21, hash: rBdd3cdf6f1e9d

Short description of error
When creating a custom keymap based on the industrial keymap, the shortcuts for switching between vertex, edge and face select (1,2 and 3) don't work after restarting Blender. It seems that the identifier ic_keymap.mesh_select_mode isn't recognized which results in Warning: property 'type' not found in keymap item 'OperatorProperties' being displayed on the console. When the preferences are opened after restarting Blender the shortcut entry doesn't display the correct title or properties in the custom keymap, however switching to the industrial keymap and then back makes it work again.

The cause of the problem seems to be that the operator IC_KEYMAP_OT_mesh_select_mode is only registered when the industrial keymap is loaded.

Correct shortcut in the industrial keymap


Shortcut in the custom keymap after creation


Shortcut in the custom keymap after restarting Blender

This issue was identified by clawjelly and reported on Blender's StackExchange.

Exact steps for others to reproduce the error

  1. Select the industrial keymap in the preferences
  2. Create a new keymap using the plus icon next to the keymap dropdown
  3. (Optional) Switch to edit mode and verify that the shortcuts 1, 2 and 3 work as intended
  4. Close Blender, then start it again
  5. Switch to edit mode and verify that the shortcuts 1, 2 and 3 do not work

Event Timeline

Robert Guetzkow (rjg) created this task.Aug 7 2019, 2:21 PM
Robert Guetzkow (rjg) updated the task description.Aug 7 2019, 2:26 PM
Robert Guetzkow (rjg) updated the task description.Aug 7 2019, 2:32 PM
Robert Guetzkow (rjg) updated the task description.Aug 7 2019, 2:35 PM
Robert Guetzkow (rjg) added a comment.Aug 7 2019, 2:38 PM

This could also be considered a design decision, however it's definitively not obvious to the user why this wouldn't work.

Robert Guetzkow (rjg) updated the task description.Aug 7 2019, 2:41 PM
William Reynish (billreynish) assigned this task to Campbell Barton (campbellbarton).Aug 7 2019, 3:21 PM
William Reynish (billreynish) added subscribers: Campbell Barton (campbellbarton), William Reynish (billreynish).

This is an issue. @Campbell Barton (campbellbarton) If we ported this to Blender proper, this would not be an issue. Should we do that?

William Reynish (billreynish) lowered the priority of this task from 90 to Low.Aug 7 2019, 3:21 PM
Campbell Barton (campbellbarton) added a comment.Aug 7 2019, 6:08 PM

Right, keymaps defining their own operators won't work, we should make this behavior possible without additional operators.

Robert Guetzkow (rjg) renamed this task from Custom keymap with shortcut for ic_keymap.mesh_select_mod doesn't work after restarting Blender to Custom keymap with shortcut for ic_keymap.mesh_select_mode doesn't work after restarting Blender.Aug 7 2019, 6:29 PM
Robert Guetzkow (rjg) updated the task description.