I like using BackgroundWorker in .NET because it ensures that the callbacks get run on the main thread. In MonoTouch 4.0, however, BackgroundWorker.RunWorkerCompleted is getting called on the background thread that is doing the work. This means I need to wrap my callback code in InvokeOnMainThread. Not horrible, but it is annoying. Is this considered a bug in MonoTouch that might get addressed at some point or is that just the way it's going to be?
-- View this message in context: http://monotouch.2284126.n4.nabble.com/BackgroundWorker-RunWorkerCompleted-runs-on-wrong-thread-tp3526376p3526376.html Sent from the MonoTouch mailing list archive at Nabble.com. _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
