views:

1923

answers:

3

OK, I should start this off by saying I'm not sure this is necessarily the right way to deal with this but...

Basically I have created a Window in WPF for displaying notifications in my application (a bit like Outlook New Mail notification). I would like to try and show this Window in it's own thread (it might do some work in the future).

I've created the Window using WPF because it's a bit nicer at handling things like AlwaysOnTop and Fading In and Out.

The application that shows the notification is a 3.5 Windows Forms App. I've seen examples similar to this SOF: C# winforms startup (Splash) form not hiding for showing a Form in a different thread however I'm unable to start a new Message Loop with the WPF Window.

I've tried just calling Notification.Show() in a new thread however the Window never displays.

  1. Is it possible to show this WPF in it's own thread?

  2. Why do I see some resources say that you should not show any UI in a separate thread?

A: 

You should display the notification using the main UI thread and if that window is going to perform any work, run that work in a background thread. You should not use more than one thread to access or create UI objects, not even if you don't share those objects between threads.

Gerco Dries
Fair enough, but why? What I mean by Why is, Why should I not create UI objects in more than one thread? I want this window to load and display without affecting the users current work
MrEdmundo
+4  A: 

The WPF Threading Model page has details on this. Look for "Multiple Windows, Multiple Threads."

Jon Skeet
Thanks, this line: System.Windows.Threading.Dispatcher.Run() makes my form show in the Thread. Don't fully understand it yet but the article gives me a direction, thanks. Interestingly the article says it is perfectly reasonable to have UI forms created on different threads.
MrEdmundo
+1  A: 
  1. Is it possible to show this WPF in it's own thread?

Absolutely. Just create a new STA thread and create and display your Window from it. I've used this technique for a splash screen because the main (UI) thread got really tied up doing other things. It was completely out of my control how much work was being done on the UI thread because of a 3rd party framework we were using.

  1. Why do I see some resources say that you should not show any UI in a separate thread?

Possibly because of the extra complexity involved. If one of your Windows wants to pass data to another, you need to remember that they're executing on separate threads. Therefore, each should use its Dispatcher to marshal calls to the correct thread.

HTH, Kent

Kent Boogaart
Hi, I've tried the new Window in a STA thread, however when I call Notification.Show() nothing is displayed.
MrEdmundo
You may need to simplify and post minimal code. It may be something simple like forgetting to start the thread ;)
Kent Boogaart