for the discussion. Does it worth to modify loading XML process, thus it could understand characters, instead of integer codes for keys.
That is an interesting question... I think in most cases the actual key, is more important.
IIRC by default Ctrl+/ comments the current line/selection. Never mind which Keycode the "/" has on the users keyboard layout.
For example, I use "Dovrak UK Punctuation".
The IDE has
ecToggleComment: SetSingle(VK_OEM_2,[XCtrl]);
which did not work for me at all.
Having "ctrl" and "key=/" instead of a keycode, could help... or could mess it up.
On a German layout the "\" is only available via AltGr. Yet on an English layout the "\" has its own key.
Having something like ctrl-\ would then break, if a German user wants to load it.
(and if the actual number needs to be specified, it could be prefixed by some character)
Actually, in that case the XML could have a "KeyCode"
<Item9 Name="Build project/program">
<KeyA Default="False" KeyCode1="117" Key1="F6" Shift1="2"/>
</Item9>
Btw, Visual Studio keyboard map XML is attached. It is based on Tango600's keyboard schema.
It will be a little time before I get to any of this. Quite busy right now.
I do think that the V.S. map is a great extension.
As for XML vs Build-in, I will wait what other devs have to say.