What is the point of PreviewKeyDown?

[Jeff Johnson]

This seems like one of the most useless events in the Forms namespace. You'd
think that it would give you the ability to examine keystrokes early on and
potentially cancel them, but cancelling is the main function it lacks.
Therefore, when would anyone EVER use this event as opposed to KeyDown?

 

[michel.desangles]

This seems like one of the most useless events in the Forms namespace. You'd
think that it would give you the ability to examine keystrokes early on and
potentially cancel them, but cancelling is the main function it lacks.
Therefore, when would anyone EVER use this event as opposed to KeyDown?

Because KeyDown won't propagate to the final Control.

Here is one use : http://blogs.msdn.com/jfoscoding/archive/2006/01/26/518181.aspx

Another : if (e.KeyChar == 27) CloseDialog();

And so on...

Michel

 

[Jeff Johnson]

Because KeyDown won't propagate to the final Control.

Here is one use :
http://blogs.msdn.com/jfoscoding/archive/2006/01/26/518181.aspx

Another : if (e.KeyChar == 27) CloseDialog();

Thanks for the link. My actual issue revolves around intercepting command
keys, and an article linked to by that one gave me some great information.