http://blogs.msdn.com/b/ericgu/archive/2003/07/18/52390.aspxWindows forms requires that certain operations happen on the main thread. I try to make this easier to use.en-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/ericgu/archive/2003/07/18/52390.aspx#52392Fri, 18 Jul 2003 21:44:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:52392EricHmm. That's an interesting alternative, but it involves a fair amount of extra plumbing in all the handler functions, which I'd like to avoid. <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=52392" width="1" height="1">http://blogs.msdn.com/b/ericgu/archive/2003/07/18/52390.aspx#52391Fri, 18 Jul 2003 10:10:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:52391Geert BaeyaertYou don't really need two methods. You can also use the Form.InvokeRequired property, which indicates whether or not you are on the thread the form was created on. InvokeRequired is, for obvious reasons, thread-safe. Your code would then look like this: // setup code object.RemoteUpdate += new UpdateHandler(RemoteUpdateFunc); public void RemoteUpdateFunc(object sender, RemoteUpdateEventArgs args) { if (InvokeRequired) this.Invoke(new UpdateHandler(RemoteUpdateFunc), new object[] {sender, args}); else { // use the values here } } Using this construct, if the event is raised on a non-ui thread, the handler will first invoke itself, executing the else branch on the second pass. In the other case, the invoke call will be skipped. Geert<div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=52391" width="1" height="1">