Normal
I'm a bit new to threading too; I know the basics, but not some of the harder stuff. I did this for a Windows Form solution, so it was easier there.The answer to your problem is that you need your class to implement the ISynchronizeInvoke interface, so then there is a mechanism for the process thread to communicate with the UI thread - all UI related calls should be done on the UI thread (funny things usually happen otherwise).Alternatively, you could try using the BackgroundWorker object, which is designed to alleviate this problem.I'll see if I can get some time this weekend to dabble with this and post some code.Sam
I'm a bit new to threading too; I know the basics, but not some of the harder stuff. I did this for a Windows Form solution, so it was easier there.
The answer to your problem is that you need your class to implement the ISynchronizeInvoke interface, so then there is a mechanism for the process thread to communicate with the UI thread - all UI related calls should be done on the UI thread (funny things usually happen otherwise).
Alternatively, you could try using the BackgroundWorker object, which is designed to alleviate this problem.
I'll see if I can get some time this weekend to dabble with this and post some code.
Sam
