| T O P I C R E V I E W |
| PaloM |
Posted - 06/28/2005 : 18:15:25
[url]http://www.vbinfozine.com/a_deh.shtml[/url] |
| 2 L A T E S T R E P L I E S (Newest First) |
| Zachary82499 |
Posted - 06/26/2006 : 03:04:08
quote:
Originally posted by PaloM
Please update the DelayedEventDispatcher.
"update" is exceptional! I love it!
[url="http://www.scuba-diving-sites.com/scuba-diving/scuba-diving-cayman.php"]Scuba Diving Cayman
[/url] - [url="http://www.car-hire-search.com/car_hire/car-hire-new-york.php"]Car Hire New York
[/url] |
| PaloM |
Posted - 07/09/2005 : 17:13:35
I've published a fix to the code accompanying the article "Delayed event handling for WinForms applications." ([url]http://www.vbinfozine.com/a_deh.shtml[/url].) This fix is available at [url]http://www.vbinfozine.com/c/deh.zip[/url].
Please download and use the updated DelayedEventDispatcher.vb/cs classes, otherwise your application can end up invoking processing for a single event multiple times.
This can happen if your event handling code yields control to Windows (for example by calling the Application.DoEvents method). In these cases, the old DelayedEventDispatcher could invoke your event handling code multiple times, sometimes even resulting in a StackOverflowException.
The fix is in the DelayedEventDispatcher.HandleEvent method (in both VB.NET and C# versions). Please update the DelayedEventDispatcher.vb/cs files in all your projects that are using them. Or, if you're using the LaMarvin.Windows.Forms.Events.dll assembly, replace the assembly in your source directory with the new one and recompile all applications that reference it.
Kudos to Matt Stone for discovering this issue. Thanks Matt!
I'm sorry for any inconvenience this might have caused to you.
Palo
|
