Note: This is with a preview 663 build, but pretty sure the problem is present in normal latest build as well.
When you are using a second monitor (+ maybe the resolution needs to be larger than main monitor, similar to many notebook with external monitor setups) then opening a WindowChrome'd window in maximised state causes rendering problems when the Window is then unmaximised (in 'normal' state).
Usually, this results in a portion of the top and left side of the window not rendering and remaining transparent (don't know if this depends on secondary monitor location or not), and in severe cases can also cause large portions of the client area to not render and be transparent as well. This is a big problem when the Window in question is the main Window!
Simplest way to reproduce this is to create new project, add the WindowChrome, and change the Window's WIndowState to Maximized. Once it runs, unmaximise and note the border rendering issues. This persists for the entire session.
If the instead the Window is changed to open in normal state, or if no external monitor is present, then all is fine.
There is also an additional bug in that during initialisation/load, if the window is moved to the secondary monitor and then maximised, it instead opens maximised on the main monitor.
I can provide a project demonstrating this, but discovered that the above was all that was needed to trigger the issue.
[Modified 5 years ago]