Qt 6.7.1 Released (opens in new tab)

(qt.io)

23 pointsfelipefar2y ago2 comments

2 comments

2 comments · 1 top-level

rubymamis2y ago· 1 in thread

I love Qt. But they should focus MORE on fixing bugs rather than adding new features. Just in the last 7 months, I found and filled 4 bugs[1] - two of which assigned as Critical. There are many other bugs that I bumped into (that have already been reported) yet still aren't fixed.

EDIT: If any Qt developer sees this, why is there no option to disable flicking of QML Flickable by mouse click yet keep letting users scroll via mouse wheel/touchpad? Setting `interactive` to false disables both. Or am I missing something?

[1] https://bugreports.qt.io/browse/QTBUG-122658

https://bugreports.qt.io/browse/QTBUG-124572

https://bugreports.qt.io/browse/QTBUG-123133

https://bugreports.qt.io/browse/QTBUG-124814

mardifoufs2y ago

Agreed. Pyside had segfaults and trivial bugs in 6.7. A super weird example was that you simply can't use qlabels for some reason, as shiboken had issues binding them correctly if you import a module (I think Pyside6.QtCore?). They weren't subclassed as QWidgets I think meaning you just couldn't upgrade. The same goes for the segfaults caused by signals. I guess it's an issue with pyside and not QT proper but still, it sure sucks when even a point release breaks stuff (had to revert 6.6.3 to 6.6.2 because again, segfaults).

It's not just my app that had those issues too. Napari also had issues with unexplained segfaults (access violations) with more recent pyside versions. Super frustrating to debug too.

j / k navigate · click thread line to collapse