hi, Don Ho :
I want to write a plugin (Vi-Mode), so need handle WM_KEYDOWN message.
(WM_KEYDOWN is before process a key, SCN_CHARADDED is after process a key)
Can you provide it in messageProc() ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
WM_KEYDOWN, WM_KEYUP and WM_CHAR with ability to change the key code (character) pressed would be great. It would give full control over Scintilla's text input to the plugins. WM_SYSKEYDOWN and WM_SYSKEYUP may be useful also - to process keys while ALT is pressed, for example.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Through it's not recommaned to plugin authors, you can subclass 2 Scintilla handles to capture WM_KEYDOWN to get job done.
Whereas SCN_CHARADDED, it can be relayed to plugins. You could get it from beNotified().
Please let me know if you really need it, then I will implement it.
Don
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hi, Don Ho :
I want to write a plugin (Vi-Mode), so need handle WM_KEYDOWN message.
(WM_KEYDOWN is before process a key, SCN_CHARADDED is after process a key)
Can you provide it in messageProc() ?
WM_KEYDOWN, WM_KEYUP and WM_CHAR with ability to change the key code (character) pressed would be great. It would give full control over Scintilla's text input to the plugins. WM_SYSKEYDOWN and WM_SYSKEYUP may be useful also - to process keys while ALT is pressed, for example.
Through it's not recommaned to plugin authors, you can subclass 2 Scintilla handles to capture WM_KEYDOWN to get job done.
Whereas SCN_CHARADDED, it can be relayed to plugins. You could get it from beNotified().
Please let me know if you really need it, then I will implement it.
Don