Is there anything wrong in WPF with setting the Owner property of a window to its parent in that parent's constructor? There shouldn't be, right? So why am I getting an XamlParseException
from the following code?
public partial class MainView : Window
{
private readonly OwnedWindow owned;
public MainView()
{
InitializeComponent();
owned = new OwnedWindow();
owned.DataContext = DataContext;
var window = GetWindow(this);
owned.Owner = this; //Setting to window causes the same error
...
}
I should clarify that removing the owned.Owner = this;
also removes the runtime error.
The details of the exception:
XamlParseException was unhandled
The invocation of the constructor on type '...MainView' that matches the specified binding constraints threw an exception.
Actually, I looked at the Inner Exception, and it says:
Cannot set Owner property to a Window that has not been shown previously.
So I'm looking into that now.
The problem is that because WPF only creates the native window the first time a WPF Window is shown, you can't be setting a not-yet-shown Window as an Owner
(since that establishes a native window "owner -> owned" relationship, but the native handle doesn't yet exist.)
You can handle the StateChanged
event on the owner window, ensure that the new state is "shown", and then set the owned window's Owner
at that point. Alternatively, you could create and show the owned window at that point.
I ended up subscribing to Window.Activated
, not Window.StateChanged
. Be sure to unsubscribe to it in the handler, as advised in the comments.
private void OnActivated(object sender, EventArgs eventArgs)
{
owned.Owner = this;
Activated -= OnActivated;
}
I accepted dlev's answer because it led me directly to finding the answer, even if his didn't work for my exact situation.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With