Community
Participate
Working Groups
I want to define CTRL+RIGHT to be "Navigate/Go Into" in the windows scope. When I do this, "Text/Next Word" in the "Editing Text" scope gets removed. This shouldn't happen, since that scope is more specific and overrides the keybinding, which is what I would want. The workaround is to go back to the "Next Word" command and re-add its original binding.
Moving Dougs bugs
Is this still a problem in 3.3? PW
yes
Created attachment 64811 [details] Binding Manager v01 The code that was supposed to build a list of all keybindings would remove any SYSTEM keybindings that it found first. PW
I recently re-encountered this bug and nearly opened a dupe of myself. The reason this is so annoying is that the conflict is often assumed but doesn't really exist. The example mentioned here already shows thi. "Go Into" is never enabled at the same time as "Next Word", yet the preference page assumes a conflict based on context inheritance, and re-maps the existing binding.
Already in I build. PW
Does the solution also handle the scenario where the two contexts are orthogonal?
Now adding a keybinding will only remove the system keybinding with the same command in the same scope. PW
In I20070501-0010 PW