Make multi-shortcut optional

[GoogleCodeExporter]

Grafx2 allows the same keyboard shortcuts to run several actions, but I feel 
it's more a problem than a feature.
For a user setting a shortcut, it's easy to run into "conflict", ie. re-use a 
key that's already assigned to a function he never uses. Even if he knows it 
was in use, he needs to find and free the other shortcut. The possible "fix" I 
wrote in another issue is still weird ergonomics, I don't really like it.
During development, we add new functions and sometimes default shortcuts for 
them, but this can be a key already used by user, which will cause confusion 
when he'll use it.

For all this I propose making multi-shortcut optional, with default value "no". 
While single-shortcut is active:
- when the user assigns an already active key, it immediately frees the 
shortcut(s) that used it.
- on program startup, when loading config file, including defaults (new) 
values, the program eliminates duplicates to keep only one action by shortcut.

Original issue reported on code.google.com by yrizoud on 29 Mar 2011 at 9:53

[GoogleCodeExporter]

Yes, it's more annoying than useful, particularly as nearly all shortcuts are 
already assigned, odds of getting a conflict are high.

Original comment by pulkoma...@gmail.com on 29 Mar 2011 at 10:04

• Changed state: Accepted
• Added labels: Milestone-2.4, OpSys-All

[GoogleCodeExporter]

Done in r1769

Original comment by yrizoud on 6 Apr 2011 at 11:12

• Changed state: Fixed
• Added labels: Milestone-2.3
• Removed labels: Milestone-2.4