On Fri, 2 Nov 2007, Dmitry Timoshkov wrote:
It's a good idea to try to have ToUnicodeEx work mainly as it does on Windows, but we are miles away from reaching this goal.
What goal are you talking about?
The goal of a implementation of ToUnicodeEx that is 100% compatible with Windows.
Since I'm very closely track all locale and keyboard input related problems current code works very well, including international keyboard input. The only feature that is missing is support
I disagree. Two examples:
1) Shift-Numlock-Del generating Backspace AND a comma, using the sv layout.
2) The race condition (bug 4923). We had to modify our Xserver to send keyboard events *slowly* to Wine, to avoid this.
With these bugs still existing, I don't thinks reasonable to say that the implementation "works very well". There are several other bugs in the Bugzilla as well, as well as 22 FIXMEs in the source.
Another interesting fact is that none expected or preferred the current Wine behaviour.
It this case it doesn't really matter what users expect or prefer, behaviour of ToUnicodeEx is predefined by what Windows does.
You are missing the point. We can have a 100% Windows compatible ToUnicodeEx but still select the model we want. It's just about what input we should feed to ToUnicodeEx. EVENT_event_to_vkey isn't a Windows API, so we can modify it how we want.
Rgds, --- Peter Åstrand ThinLinc Chief Developer Cendio AB http://www.cendio.se Wallenbergs gata 4 583 30 Linköping Phone: +46-13-21 46 00
ThinLinc User Group 2007 Höstkonferens --- 15-16 november, Linköping. Program och anmälan: http://www.thinlincusergroup.se/aktiviteter