Michael- inline with ***
How does it work in this scenario? WinApp creates object, Object creates thread for internal work, The internal work call Methods witin the object to process data, (is this bad, calling methods in an object from a thread method call?) Sometimes the object in turn fires an event for the WinApp to receive, In the event handler in the WinApp I update a text box. *** How are you accomplishing this? I don't think you'll have an issue. It looks like you are raising the event on one thread and catching it on the thread that the GUI components are running on. What thread is doing the update? Do I have to use control.invoke here? What if I don't, what the worst that could happen? *** The worst that could happen would be inconsistent behavior. Essentially, you wouldn't be able to guarantee that the bahavior would be correct in all circumstances. Secondly, are there examples of what goes wrong when you don't use control.invoke. I used to rememeber that all code examples came with 2 examples. One example showed what would go wrong when you do something a certain way and then it would show the correct way. The wrong way made it very easy to understand what was going on. *** I don't know of any off the top of my head. Jacob A. Grass You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
