Question

I’m aware, and use, the xxx.Dispatcher.Invoke() method to get the background thread to manipulate GUI elements. I think I’m bumping up against something similar, but slightly different, where I want a long running background task to construct a tree of objects and when done hand it to the GUI for display.

Attempting to do that results in an InvalidOperationException, “due to the calling thread cannot access this object because a different thread owns it.” Curiously, this doesn’t happen with simple type.

Here’s some example code that demonstrates a trivial case the throws the exception. Any idea how to work around this? I’m pretty sure that the problem is the background thread owns the factory constructed object and that the foreground GUI thread can’t take ownership, although it works for more simple system types.

private void button1_Click(object sender, RoutedEventArgs e) 
{  
   // These two objects are created on the GUI thread
   String abc = "ABC";  
   Paragraph p = new Paragraph();

   BackgroundWorker bgw = new BackgroundWorker();

   // These two variables are place holders to give scoping access
   String def = null;
   Run r = null;

   // Initialize the place holders with objects created on the background thread
   bgw.DoWork += (s1,e2) =>
     {
       def = "DEF";
       r = new Run("blah");
     };

   // When the background is done, use the factory objects with the GUI
   bgw.RunWorkerCompleted += (s2,e2) =>
     {
        abc = abc + def;         // WORKS: I suspect there's a new object
        Console.WriteLine(abc);  // Console emits 'ABCDEF'

        List<String> l = new List<String>();  // How about stuffing it in a container?
        l.Add(def);                           // WORKS: l has a reference to def

        // BUT THIS FAILS.
        p.Inlines.Add(r);  // Calling thread cannot access this object
     };

   bgw.RunWorkerAsync();
}

The grand scope of the problem is that I have a large document that I’m constructing on the fly in the background and would love for the GUI to show what’s been generated so far without having to wait for completion.

How can a background worker act as an object factory and hand off content to the main thread?

Thanks!

Answer 1

You are trying to create the Run in the background thread, but Run is a FrameworkContentElement which inherits from DispatcherObject and thus is bound to the thread that created it.