Community
Participate
Working Groups
I20070503-1400 The new Keys pref page makes it easy to create unnoticed conflicts. On the old page, the user immediately saw all commands with the same keybinding as the one currently entered and could then decide whether the conflict is acceptable (e.g. because the bindings are active in different contexts) or not. A possible fix would be to add a new column (or rename the 'User' column to 'Status') and add icons for - conflict - conflict in different contexts That would still not immediately show the conflicts, but if the user is aware of a conflict, she can easily sort the table by bindings and then see the other bindings in the surroundings.
Bindings with the same key sequence could also be dynamically added to the table, e.g. just after the entry being modified (regardless of the sort order) and with a different bg color.
I'm working this one under bug 185150 PW *** This bug has been marked as a duplicate of bug 185150 ***