ImmGetVirtualKey
Functional Difference from WIN95
The HWND should be associated to IMM context.
Functional Difference from SBCS Open32
'N/A'
Implementation
T.B.DA PM WM_CHARX1 message on OS/2 NLS environmrnt is translate to a Win95 WM_KEYDOWN/VK_PROCESSKEY. As the PM WM_CHARX1 message has a PM character code and the PM scan code, the character code and the scan code are translate to a Win95 virtual-key code, and it is saved in a ImmGetVirtualKey() internal work area. After that the ImmGetVitualKey() can return a Win95 virtual keycode.
Behavior using 16 bit IME
You can use this function as same as 32bit IME.