Removing and readding hotkeys adds them in the wrong section of the keymap #65343

New Issue

Reiner Prokein · 2019-05-31T09:36:50+02:00

Reiner Prokein commented

2019-05-31 09:36:50 +02:00

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35

Blender Version
Broken: version: 2.80 (sub 72), branch: blender2.7, commit date: 2019-05-29 18:17, hash: fee600f479
Worked: (optional)

Short description of error
[Please fill out a short description of the error here]

When you remove let's say the hotkey to call the toolbar in the 3D view, and then readd it, then it gets readded in the wrong section of the keymap. The result is that this hotkey may be troubled now. See example below.

This behaviour breaks the functionality to manage your hotkeys from within the right click menu of the operators in the UI. This is a showstopper bug for user configured keymaps.

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

Open Blender. In the View menu of the 3D view remove the hotkey for Toolbar. This hotkey is local, just for the 3D view. It's initally located in the generic section of the 3D view.

Now readd the hotkey. Watch in the keymap where it gets readded. In the Window section. And this section acts global.

Now switch to the Scripting Layout. Press the hotkey that you have readded in the 3D View. You will get a error message now. The hotkey is now global, it is in the Windows section. But the toolbar does not exist in the Text editor. And so we get a error message.

**System Information** Operating system: Windows-7-6.1.7601-SP1 64 Bits Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.35 **Blender Version** Broken: version: 2.80 (sub 72), branch: blender2.7, commit date: 2019-05-29 18:17, hash: `fee600f479` Worked: (optional) **Short description of error** [Please fill out a short description of the error here] When you remove let's say the hotkey to call the toolbar in the 3D view, and then readd it, then it gets readded in the wrong section of the keymap. The result is that this hotkey may be troubled now. See example below. This behaviour breaks the functionality to manage your hotkeys from within the right click menu of the operators in the UI. This is a showstopper bug for user configured keymaps. **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue] [Based on the default startup or an attached .blend file (as simple as possible)] Open Blender. In the View menu of the 3D view remove the hotkey for Toolbar. This hotkey is local, just for the 3D view. It's initally located in the generic section of the 3D view. Now readd the hotkey. Watch in the keymap where it gets readded. In the Window section. And this section acts global. Now switch to the Scripting Layout. Press the hotkey that you have readded in the 3D View. You will get a error message now. The hotkey is now global, it is in the Windows section. But the toolbar does not exist in the Text editor. And so we get a error message. ![deleteandreadd.jpg](https://archive.blender.org/developer/F7081064/deleteandreadd.jpg) ![shifttinscripting.jpg](https://archive.blender.org/developer/F7081066/shifttinscripting.jpg)

Reiner Prokein commented

2019-05-31 09:36:50 +02:00

Added subscriber: @tiles

Campbell Barton was assigned by Sebastian Parborg

2019-06-13 15:19:11 +02:00

Campbell Barton commented

2019-06-20 08:05:40 +02:00

There are two issues here:

Guessing the current keymap doesn't always work, there should be a key-map selector in the popup that assigns a key.
We could do a better job guessing in this case (check RNA properties for operator buttons - currently only the operator is checked).

Setting as low priority since this isn't a regression since 2.7x.

There are two issues here: - Guessing the current keymap doesn't always work, there should be a key-map selector in the popup that assigns a key. - We could do a better job guessing in this case (check RNA properties for operator buttons - currently only the operator is checked). Setting as low priority since this isn't a regression since 2.7x.

Campbell Barton was unassigned by Dalai Felinto

2019-12-23 16:34:14 +01:00

Dalai Felinto commented

2019-12-23 16:34:14 +01:00

Added subscriber: @ideasman42

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Removing and readding hotkeys adds them in the wrong section of the keymap #65343