4 ms·
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
by hermitcrab 2y ago
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.
- ramesh31 2y agoThis is my stock response when anyone complains about CSS; consider the alternatives.
- 01HNNWZ0MV43FF 2y agoI found Qt way easier around 2010, maybe the new flexbox stuff is good though?
- layer8 2y agoWith CSS you typically need a lot of trial and error, and then there’s different browser implementations and versions on top of that.
- hermitcrab 2y agoI prefer Qt layout to CSS any day.
- drivingmenuts 2y agoI 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 2y agoI 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 2y agoQt 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.
- hermitcrab 2y agoQt 6 is supposed to handle high DPI better. Does that not apply to multiple monitors? I have not noticed any issues.
- Remnant44 2y agoI 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.