Question

I have a SWF object embedded in a WindowsFormsHost Control inside a WPF window.

I’d like to add a toolbar over the swf movie.

The problem with the snippet of code I have below, is that when the new child is added to the host control (or the movie is loaded, I haven’t figured out which yet), the toolbar is effectively invisible. It seems like the z-index of the swf is for some reason set to the top.

Here is what it looks like:

XAML:

<Grid Name="Player">
   <WindowsFormsHost Name="host" Panel.ZIndex="0" />
   <Grid Name="toolbar" Panel.ZIndex="1" Height="50"
      VerticalAlignment="Bottom">
           [play, pause, seek columns go here]
   </Grid>
</Grid>

C#:

private void Window_Loaded(object sender, RoutedEventArgs e)
{
   flash = new AxShockwaveFlashObjects.AxShockwaveFlash();
   host.Child = flash;
   flash.LoadMovie(0, [movie]); // Movie plays, but no toolbar :(
}

Any insight on this issue would be much appreciated.

---

Update: Since no suitable answer was posted, I’ve placed my own solution below. I realize this is more of a hack than a solution so I’m open to other suggestions.

Answer 1

Another solution I’ve discovered is to use Windows Forms’ ElementHost control. Since I’m using a Windows Form inside a WPF window anyway, why not just use an entire Windows Form and save myself Z-Issue headaches.

The ElementHost control is really useful, because I can still use my toolbar UserControl, and embed it inside the Windows Form. I’ve discovered that adding a child can be finicky with Windows Forms, so here’s a snippet describing the solution:

First, toss in the ActiveX object, then an ElementHost Control, using the designer.

Form1.Designer.cs:

private AxShockwaveFlashObjects.AxShockwaveFlash flash;
private System.Windows.Forms.Integration.ElementHost elementHost1;

Form1.cs

public Form1(string source)
{
     InitializeComponent();
     toolbar = new UserControl1();
     this.elementHost1.Child = this.toolbar;
     this.flash.LoadMovie(0, source);
}

Note that the child was not set in the designer. I found that for more complex UserControls the designer will complain (though nothing happens at runtime).

This solution is, of course, still not entirely ideal, but it provides the best of both worlds: I can still code my UserControls in XAML, but now I don’t have to worry about Z-indexing issues.