When creating a WPF window with AllowsTransparency=\"True\" WindowStyle=\"None\"
and maximizing it via this.WindowState = WindowState.Maximized;
the Wi
Unfortunately there is no good solution to this other than to make a WindowStyle="None"
window without resizing, and handle everything yourself. This means your own maximize/minimize/restore buttons that set the window dimensions to fit the screen. Your own live caption area for dragging. Your own borders with the appropriate cursors. Your own double-click handler to maximize/restore. Your own routine for checking the mouse position against the height of the screen for drag-to-dock. Etc. You get the idea. It's a pain in the neck, but if you do it once at least you'll have it for all future projects. Unfortunately you will lose the "Aero" animations, but alas.
I also want to point out one reason why this issue is very important. In at least some cases, WPF can't make full use of accelerated graphics when windows span two monitors (as they normally do any time a window is maximized). That means performance of D3DImage
, as well as any Effect
, suffers when the window is maximized. It was happening for me, and many of my users, which is what drew my attention to this issue.