In these scenarios, I actually tend to prefer that any Windows Forms code is the one that makes sure all calls from the outside world are done on the right thread.
After all, it's a Windows Forms limitation. Why should the client have to be concerned with the inner requirements of yourself are, and pollute themselves with WinForms "magic"? On 5/19/06, Alexander Herrmann <[EMAIL PROTECTED]> wrote:
But I recently found the solution or better the solution why this wasn't working. When using Windows.Forms you have to explicitly invoke the methods that should do their work in other threads than the UI thread.
=================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
