Re: [AD] Keyconf problem?

[Elias Pschernig <elias@xxxxxxxxxx>]

On Sat, 2005-01-22 at 15:08 +0100, Evert Glebbeek wrote:
> On Saturday 22 January 2005 14:47, Elias Pschernig wrote:
> > Hopefully this will fix itself after someone finds the windows function
> > to translate a directx scancode to unicode, and we can drop pckeys.c.
> 
> If you're bored, you may want to have a look at the following function I 
> just found on MSDN (ToUnicode):
> 
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/
> winui/windowsuserinterface/userinput/keyboardinput/keyboardinputreference/
> keyboardinputfunctions/tounicode.asp
> 
> I can make head nor tail of the explanation given, but it seems to do 
> something to a scancode and produce a unicode character.
> 

Looks exactly like what is needed though. I guess, DirectX will return
the scancode and VK - and then we get the unicode (from the current
windows locale) with this, and can directly send it to keyboard.c,
bypassing pckeys.c. I'll try to make a patch, can't promise that it will
be anytime soon though. So if a windows user wants to try it instead..

-- 
Elias Pschernig