Running your latest test solution (so your version of the product) on divers hardware over here.
All systems Win10 pro latest updates and hardware latest (stable) drivers.
- On one laptop (single screen - resolution 1600x900 - NVidia GeForce 940mx) it works fine.
- On dual monitor desktop system (System A) (one monitor 1920x1080, other 1920 x 1200) it works fine on the 1920x1080 but not on the 1920x1200 (the ribbon is back).
- On triple monitor desktop system (my developer system) (System B) (all tree monitors 1920x1080) the problem (the ribbon) occurs on all tree monitors.
- Also ran it (the bin directory and install of .Net 5 runtime) on divers other PC's and laptops, all mono screens (except one laptop dual screen) and it all worked fine.
Apparently one has to be unlucky to have this issue and somehow multi-monitor is a condition (but not always). The connections are done via divers ports and that is in my opinion not the condition (for instance on one system the monitor connected via hdmi is fine, on the other system hdmi monitor gives the problem).
If this issue is not mentioned by others, I presume at runtime (at clients thus) it does not occur (much) and I can live with that. For you internally, I have provided some more data on these two systems :
- On 'System A' both monitors are plugged into one NVidia Geforce GTX 1050 Ti card.
- On 'System B' two monitors are connected with one Graph card (NVidia GeForce GTX 1660 Super) and one monitor is wired up with the second Graph card in the system (NVidia GeForce GTX 1650).
- On these both systems (A & B), dozens of other software programs (development and non-development software) are used daily and no other program shows that same problem/behavior. For development not .NET/devexpress, not default wpf window, not winforms, not c++/QT (QML) not Java (both JavaFX and swing), not Delphi (firemonkey) ...
Sharing screens holds security risks and is therefore not permitted. Sorry for this inconvenience but it is what it is.
Cheers,
Geert