I've caught up on reviewing some issues that were introduced in 2011.
One occurs when a single letter shortcut shares the same first letter of other two character shortcut. It does not appear first in the order but should. This prevents single shortcuts from being matched on the first try so they can then be executed with the spacebar.
Another item is only defined shortcuts export to XML. This makes it more difficult for someone to setup their standards outside of Revit.
In both these cases the solutions look straightforward. What I appreciated in investigating these was the subtlety of the usage. In each release we define new commands and they require shortcuts. We would like to define these using the best practices so it would be great to hear how people approach setting theirs up - not just for me but for all the readers.
Here are a couple simple suggestions to start:
Avoid defining shortcuts that are far apart on the keyboard. "WA" is better for Wall than "WL"
In 2011 the use of accelerators such as Cntrl or Alt should expand the number of combinations and allow one to group many shortcuts on a single side of the keyboard.
This is subtle but could be used when characters in the word are already in-use. In English for instance PH can replace an F sound. The idea is to be able to find a sound that evokes the command and then find characters that make the sound.
There are many types of mnemonics "WA" evokes the sound of "Wall' better than "WL"
Acronyms can also be used such as the way "Roy G Biv" symbolizes the colors of the spectrum (Red, Orange, Yellow, Green, Blue, Indigo, Violet). In Revit the shortcut of "ER" might be used for "Editing Requests"
These are just a couple examples to get people thinking and sharing. What criteria and systems are you using?