VA uses the system's keyboard layout by default. The layout selection from the options screen was added some time ago for pack creators and is probably almost NEVER used. I shouldn't have added it, but it seemed helpful at the time.
If I understand correctly, that option affects the visual representation of the keycodes in dialogs, not the way keycodes are processed.
If you are in the
US, '3 #' is displayed. If you are in the UK, '3 £' is displayed.
E.G. if I map the key above "Tab", left of "1", to a command in VoiceAttack, and send that profile to someone with a different layout, there is not guarantee that the physical location of the key that triggers the command will be the same.
The OP's intent is to automatically compensate for this difference across different layouts, to match the physical locations of the original layout, even though they represent different characters.
What could be an alternative solution, should it be implemented, is
this feature request, which was made with exactly this problem in mind.
That said, I'm still of the opinion that parsing the game's settings file is the right way to go, so you can account for keys that have been rebound away from their original locations while removing the requirement for the end user to press or otherwise manually assign keys.
Gary, as an aside, if you do keep it, the tooltip for the "Keyboard Display Layout :" label is a duplicate of the speech engine one: "This is the speech engine that VoiceAttack will use (you will rarely need to change this)".