Key Down event on editor not working

Matt, I don't believe anything has changed in the key processing area in quite some time so I suspect it's something in your application. If you think there is a problem with SyntaxEditor then please put together a tiny sample project showing the issue and email it over. Thanks!

Great news I can reproduce this with just a simple syntax editor control on the form. However it's the KeyPress event which is behaving weird, not keydown. If you place a break point at the start here after pressing the Ctrl - S keys. You should see the KeyChar property value of the KeyPressEventArgs object is equal to 19 '!!' , this is what the watch window reports.

Hi Matt,

KeyPress is not a good place to look for keys with modifiers pressed (like Ctrl+S). You should be using KeyDown or our SyntaxEditor.KeyTyping event for that.

Hi Support gang,
I am also having this problem of how to capture (CTRL+some-other-key).
The suggestion in the previous answer does not work - eack keyboard key that gets pressed is processed seperately and strange args.KeyData values (in the KeyTyping Event Handler method).
Could you please provide some specific advice how to handle the CTRL-key sequences as an aggregated "pair".
Many thanks

Both KeyPress and KeyDown events end up filtering down through our KeyTyping event, which is why we recomment people use Keytyping to handle keys instead.

Our control should only capture key events if there is a command binding to that key. KeyTyping lets you cancel the binding and if cancelled, will not mark it as e.Handled in KeyPress or KeyDown.

As for "chord" keys, those are tricky. Basically you'd have to ensure that no chord start key shortcut matches any of the command bindings. Either that or cancel in KeyTyping if it does.