Threads and UI Control - Invoke?

[Guest]

Hi all,

I have an application which has a thread that raises events. The event
handler updates the UI.

When do I need to call Control.Invoke? I understand this is required for
control method calls... but how about properties? Can I safely assign
properties from a separate thread without using .invoke?

Thanks.

 

[Tim Wilson]

No. Always use one of the invoke methods to update a control when operating
under a different thread. You can use the controls InvokeRequired property
to determine whether or not you need to invoke. See the blog entry at the
link below for more.
http://blogs.msdn.com/jfoscoding/archive/2005/05/26/422405.aspx

 

[Alexander Ogol]

I have an application which has a thread that raises events. The event
handler updates the UI.

When do I need to call Control.Invoke? I understand this is required for
control method calls... but how about properties? Can I safely assign
properties from a separate thread without using .invoke?

As adding to answer by Tim:
MSDN in most cases states what methods are thread-safe and what are not. In
Windows.Forms, [almost] all controls have thread-safe
BeginInvoke()/EndInvoke()/Invoke() methods and InvokeRequired property only.
Properties are in fact usual get_/set_ methods, just a syntantic sugar;
usual rules are used.