tag:blogger.com,1999:blog-15758573.post112975001007533833..comments2023-11-03T10:15:55.638+02:00Comments on Why not? (Ilan Assayag's blog): Making GUI Thread Programming in C# easier - take 2Ilan Assayaghttp://www.blogger.com/profile/05885131038068500210noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-15758573.post-1132538455801457222005-11-21T04:00:00.000+02:002005-11-21T04:00:00.000+02:00Thanks for clarifying in your post. As for your fe...Thanks for clarifying in your post. As for your feature request - I'm not totally sure I understand, could you elaborate? I think what you're saying is that you want SafeInvokeHelper to be able to invoke private methods, not just public ones -- but i'm not sure. Perhaps you could leave an example as a comment on my blog?<BR/>Thanks,<BR/>JohnAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-15758573.post-1131932949222960742005-11-14T03:49:00.000+02:002005-11-14T03:49:00.000+02:00I wouldn't necessarily say it fixes that same exac...I wouldn't necessarily say it fixes that same exact problem... BackgroundWorker facilitates the implementation of one very specific (yet admittedly common) scenario where you want to do some work on a new thread and safely notify the UI thread of progress and completion. SafeInvoke lets you call *any* UI function, not just progress indicator code. It also allows you to do this with just one line rather than instantiating a new component and handling events. Thanks for mentioning my post btw.Anonymousnoreply@blogger.com