So why can't you use ToUnicode() to translate the virtual key code or the scan key code into the unicode character?
Sure I can return 42 the magic number from LMGetKbdType() meaning you are using as Estonia keyboard, or maybe 78 for Devanagari keyboard in the Indian Language Kit, however it's unlikely I or any other developer will want to code the keyboard to ascii/macroman/unicode whatever translation tables in the image.
On 29-Mar-06, at 4:16 PM, Andreas Raab wrote:
Michael Rueger wrote:
I'm not quite sure about the consequences for some of the weirder keyboard layouts though:
From a user's point of view (what the user thinks he pressed) ctrl-shift-VK_1 on "normal" keyboards would mean ctrl-!, on French ones it would mean ctrl-1 .
Ah, keyboard layouts. What a pain. Can we please (please, please, please!) not require VMs to deal with those? It's a pain and it's a mess and I'd rather have some image code deal with it. So, instead of extending keyboard events, how about simply reporting a "keyboard layout identifier"[*] that the image can use to map keys reported by the VM into whatever it wants to?
[*] On Windows, that would be an identifier from GetKeyboardLayoutName (http://msdn.microsoft.com/library/ default.asp?url=/library/en-us/winui/winui/windowsuserinterface/ userinput/keyboardinput/keyboardinputreference/ keyboardinputfunctions/getkeyboardlayoutname.asp)
Cheers,
- Andreas
-- ======================================================================== === John M. McIntosh johnmci@smalltalkconsulting.com 1-800-477-2659 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ======================================================================== ===