thanks!
sure enough, using ADI for the worker-to UI thread works w/o problems. fyi, i switched to the EventHandler style only because the MSDN article did so -- they were showing how one can make a custom progress class, pass in custom events, etc..
btw, i found what the problem was w/ my line. i had converted the MSDN article from C# to VB, but didnt include something needed for VB...:
Me.BeginInvoke(New System.EventHandler(UpdateUI), eventArgs)
should be:
Me.BeginInvoke(New System.EventHandler(AddressOf UpdateUI), eventArgs)
but i checked out the BackgroundWorker class:
http://msdn2.microsoft.com/en-us/library/system.componentmodel.backgroundworker(vs.80).aspx
...awesome! this is the dream-solution i was wondering why didnt exist. but (wait for it) im on .NET v1.1.... doh! no love for me. so ugliness it is.
thanks man.
matt
sure enough, using ADI for the worker-to UI thread works w/o problems. fyi, i switched to the EventHandler style only because the MSDN article did so -- they were showing how one can make a custom progress class, pass in custom events, etc..
btw, i found what the problem was w/ my line. i had converted the MSDN article from C# to VB, but didnt include something needed for VB...:
Me.BeginInvoke(New System.EventHandler(UpdateUI), eventArgs)
should be:
Me.BeginInvoke(New System.EventHandler(AddressOf UpdateUI), eventArgs)
but i checked out the BackgroundWorker class:
http://msdn2.microsoft.com/en-us/library/system.componentmodel.backgroundworker(vs.80).aspx
...awesome! this is the dream-solution i was wondering why didnt exist. but (wait for it) im on .NET v1.1.... doh! no love for me. so ugliness it is.
thanks man.
matt