I did a quick test: I bypassed that test and now, apparently, it finally works perfectly.
Sincerely,
Carlo Bramini
---------- Initial Header -----------
From : ros-dev-bounces@reactos.org
To : "ReactOS Development List" ros-dev@reactos.org Cc : Date : Sat, 21 Jul 2007 01:07:44 -0500 Subject : Re: [ros-dev] Strange code into ToUnicodeEx().
carlo.bramix wrote:
Hello, I debugged a bit on ReactOS because I wanted to understand why my (newer upcoming) version of ReactOS Calc doesn't work when you press some keys on the keyboard. The cause of the problem is this piece of code:
int STDCALL ToUnicodeEx( UINT wVirtKey, UINT wScanCode, PBYTE lpKeyState, LPWSTR pwszBuff, int cchBuff, UINT wFlags, HKL dwhkl ) { int ToUnicodeResult = 0;
if (0 == (lpKeyState[wVirtKey] & KS_DOWN_BIT)) { ToUnicodeResult = 0; } else { ......
In other words, a key can be translated only if it's pressed and not during the release stage. Is there a reason for this choice?
Sincerely,
Carlo Bramini
Oh!!!! Yuck! it's a wine thing'y!
dlls/winex11.drv/keyboard.c:2365: * ToUnicodeEx (X11DRV.@) dlls/winex11.drv/keyboard.c:2382:INT X11DRV_ToUnicodeEx(UINT virtKey, UINT scanCode, LPBYTE lpKeyState,
dlls/user32/input.c:631:INT WINAPI ToUnicodeEx(UINT virtKey, UINT scanCode, LPBYTE lpKeyState
Maybe we need to update our code tree? James _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
------------------------------------------------------ Scegli infostrada: ADSL gratis per tutta lÂ’estate e telefoni senza canone Telecom http://click.libero.it/infostrada