Follow-up Comment #1, bug #25005 (project gnustep):
The problem here is that we don't use TranslateMessage() in the message loop,
that way we only get the raw key up and down events, not that translated char
events. But if we change to that we have no way of handling non-character key
events correctly. What we need is some sort of TranslateMessage() replacement
that would just result in the characters for the key event, sadly I don't know
if anything like this exists at all and would also not know how to write it.
I had a deeper look into what Windows offers here and the function
ToUnicode() that we are using is almost the best to do the key down message to
string conversion. The only better solution would be ToUnicodeEx() which
allows to hand in a keyboard layout as well. Could you please test if this
makes any difference for you, if it does I will update the code.
You will need to change the line
result = ToUnicode(wParam, scan, keyState, unicode, 5, 0);
inot something like
result = ToUnicodeEx(wParam, scan, keyState, unicode, 5, 0,
GetKeyboardLayout(0));
But I expect this not to change anything.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?25005>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
