I thought a good test for the patch would be this: http://blogs.msdn.com/jfoscoding/archive/2006/01/26/518181.aspx
The premise is that consumers of the event can change fields in the PreviewKeyDownEventArgs to tell the system whether or not they should get the actual KeyDown event. Unfortunately, this patch does not pass this test. However, I don't think it's entirely a result of this patch. It looks like our keyboard message processing may be broken elsewhere. An unbelievable resource about keyboard messages and events is here: http://blogs.msdn.com/jfoscoding/archive/2005/01/24/359334.aspx but I haven't compared it to our implementation. I don't know if we have a resident keyboard event guru or not. :) Jon George Giolfan wrote: > > > > > > ____________________________________________________________________________________ > Don't get soaked. Take a quick peek at the forecast > with the Yahoo! Search weather shortcut. > http://tools.search.yahoo.com/shortcuts/#loc_weather > > > ------------------------------------------------------------------------ > > _______________________________________________ > Mono-winforms-list maillist - [email protected] > http://lists.ximian.com/mailman/listinfo/mono-winforms-list _______________________________________________ Mono-winforms-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-winforms-list
