[hermitcrab]

Managing widget size and layout in complex UIs is definitely one of the more challenging aspects of programming with Qt. But you usually get what you want with a bit of trial and error.

[drivingmenuts]

I am running up against it now. While QT works on the major OSes, it somehow manages to not quite fit with the design of the OS - which drives me crazy. If I wanted it to sort of behave like a Windows app, I'd write Windows apps. Sadly, it's the best option for Python.

[hermitcrab]

I think Qt looks and feels pretty native on Windows. It doesn't look quite as native on Mac, but it's not far off.

[joezydeco]

Qt has a chronic problem with High DPI displays, especially when mixed with a lower DPI display in a multiple monitor situation. You will never get it 100% right and when you start shipping it to users that percentage will fall quickly.

[Remnant44]

I haven't had a high DPI issue with QT in quite a while. Early in QT 5, high DPI presented many problems, but they have been slowly settled over time, including by using sane defaults.

Source: I develop a QT widget app and develop on a workstation with mixed high and low DPI monitors.

[hermitcrab]

Qt 6 is supposed to handle high DPI better. Does that not apply to multiple monitors? I have not noticed any issues.

[ramesh31]

This is my stock response when anyone complains about CSS; consider the alternatives.

[01HNNWZ0MV43FF]

I found Qt way easier around 2010, maybe the new flexbox stuff is good though?

[layer8]

With CSS you typically need a lot of trial and error, and then there’s different browser implementations and versions on top of that.

[hermitcrab]

I prefer Qt layout to CSS any day.