nuukiaworld
13-01-2006, 07:30 PM
Has anyone successfully reversed the alphanumeric mode (which is started by sending MSG_ALPHANUMERIC_MODE)?
I noted the following:
0xCA (MSG_KEYPRESS_CHAR/ASCII) messages are not sent at all
0xCB is sent when pressing a character key first time, argv[0] contains the char code
0xCC is sent when pressing same key again, argv[0] contains the new char code
0xD0 is sent when timeout for successive keypresses expires (displays the cursor again)
I have still no idea how to handle the following:
0xCB is sent also if the key contains only one character (most keys on KBT_HEX). How you can know when you must show the cursor after 0xCB and when not?
In built-in dialogs, when there is no space left, every keypress sends 0xCB. How this "buffer full" condition can be told to the thing sending the key codes?
Has anyone reversed the built-in dialogs and know how you should handle these messages?
I noted the following:
0xCA (MSG_KEYPRESS_CHAR/ASCII) messages are not sent at all
0xCB is sent when pressing a character key first time, argv[0] contains the char code
0xCC is sent when pressing same key again, argv[0] contains the new char code
0xD0 is sent when timeout for successive keypresses expires (displays the cursor again)
I have still no idea how to handle the following:
0xCB is sent also if the key contains only one character (most keys on KBT_HEX). How you can know when you must show the cursor after 0xCB and when not?
In built-in dialogs, when there is no space left, every keypress sends 0xCB. How this "buffer full" condition can be told to the thing sending the key codes?
Has anyone reversed the built-in dialogs and know how you should handle these messages?