Quantcast
Channel: Extended WPF Toolkit™ Community Edition
Viewing all articles
Browse latest Browse all 4964

New Post: AvalonDock - overlaying a floating window; zIndex issue

$
0
0
Hi Boucher,

thanks for looking into this!

Unfortunately, these modifications didn't quite work out for me - e.g. while the SC_MOVE event was called, setting it to handled = true didn't have any effect on moving the window.

Is it correct that the FloatingWindowContentHost is not the entire floating window as such, but just the content area within the floating window - i.e., everything that ISN'T red in this image?

Image

If so, what is the reason behind using a HwndHost here; is this just to be able to host WinForm controls or something like Win32 Windows inside avalondock? Would there be a need to use HwndHost if my project only ever used plain WPF controls?

I've just tried replacing the FloatingWindowContentHost by a simple Contentpresenter by changing the function
    public abstract class LayoutFloatingWindowControl : Window, ILayoutControl
    {
        // ... other functions etc ...

        static object CoerceContentValue(DependencyObject sender, object content)
        {
            return new ContentPresenter() { Content = content };
            //don't use this anymore: return new FloatingWindowContentHost(sender as LayoutFloatingWindowControl) { Content = content as UIElement };
        }
    }
At first glance, this works fine. My OVERLAY_GRID correctly hides the entire window now, all other functions seem to be working as usual too.
Can you think of any side effects though, or does this seem like an ok solution if I plan to only host WPF (no WinForms) controls?

Thanks!

Viewing all articles
Browse latest Browse all 4964

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>