Diggory Hardy

I see the same behaviour (basically) on Wayland: - screen is 3840 × 2160 at 150% (but because of stupid reasons, Wayland clients see scale factor 200%) - max window...

Scale factors 100% and 150%: [logs.zip](https://github.com/rust-windowing/winit/files/8247146/logs.zip)

Hopefully this is better? [log.gz](https://github.com/rust-windowing/winit/files/8251214/log.gz) Not sure what you mean by the winit log since it doesn't appear to have one (here I enabled trace level but minimised the noisy...

KDE/kwin actually. The real question is not so much why the compositor resized the window on Alt+Tab but why it resized it after construction: ``` Scale factor: 2 Min inner...

But the behaviour I *see* is that the window is too large on construction, but the correct size after Alt+Tab. Hence `[email protected]_window_geometry(0, 0, 968, 1423)` and `[email protected]_max_size(968, 1423) ` are...

In fact, the KAS toolkit "cheats" by looking up the scale factor from the previous window constructed or (initially) from the list of available screens, thus it calculates the size...

> You don't know scale factor your window will use even if you probe all monitors. You can't just assume that it's 2, you should use 1, and wait for...

So, on X11, using my scale-factor-detection methodology and physical pixels: ``` Scale factor: 1.5 Min inner window size: Size(221, 166) Max inner window size: Size(727, 1114) Resized to: PhysicalSize {...

Apparently I made a mistake above: after the window is constructed, the render scale factor is known, and the toolkit can re-calculate layout using that immediately: ``` Initial scale factor:...

Yes, that's about what I just came up with.