On Mon Jun 3 09:58:36 2024 +0000, Zhiyi Zhang wrote:
Changing the thread dpi awareness context before moving the desktop
window, like wineandroid was doing, shouldn't be necessary, assuming that the desktop window is always per-monitor aware. I don't think this is correct. The explorer exe has "<dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">true</dpiAware>", which is system aware instead of per-monitor aware according to https://learn.microsoft.com/en-us/windows/win32/hidpi/setting-the-default-dp...
Well, I don't know if we need to replicate that?
In win32u we explicitly return per-monitor aware for the desktop window. We could set the context here to guard against any future changes on the desktop window DPI awareness but it's also unnecessary right now.
We could also make explorer process explicitly change its awareness on startup, and maybe that's something we should do regardless?