Are you finding recent Qt versions buggy on macOS?
-
Are other developers finding recent versions of Qt buggy on macOS, or is it just me?
I quickly wrote up some notes on my struggles to find a usable version of Qt that works on recent macOS releases:
https://successfulsoftware.net/2018/11/02/qt-is-broken-on-macos-right-now/
I thought other people might find them useful.
Here is hoping that Qt 5.12.0 is less buggy on macOS.
-
Hi,
Please define "recent version of macOS".
-
Are other developers finding recent versions of Qt buggy on macOS, or is it just me?
I quickly wrote up some notes on my struggles to find a usable version of Qt that works on recent macOS releases:
https://successfulsoftware.net/2018/11/02/qt-is-broken-on-macos-right-now/
I thought other people might find them useful.
Here is hoping that Qt 5.12.0 is less buggy on macOS.
@AndyBrice said in Are you finding recent Qt versions buggy on macOS?:
Are other developers finding recent versions of Qt buggy on macOS, or is it just me?
I find recent Qt versions to be buggy on all platforms, to be honest. It would be cool if more focus was placed on bug fixing and (a bit) less on new features, as it gets to a point now where I'm afraid to upgrade Qt nowadays... and I used to run beta versions regularly because things were so stable.
Anyway, that is a very subjective thing, and depends heavily on which parts of Qt you're using. Some are more stable than others.
(Z(:^
-
@AndyBrice said in Are you finding recent Qt versions buggy on macOS?:
Are other developers finding recent versions of Qt buggy on macOS, or is it just me?
I find recent Qt versions to be buggy on all platforms, to be honest. It would be cool if more focus was placed on bug fixing and (a bit) less on new features, as it gets to a point now where I'm afraid to upgrade Qt nowadays... and I used to run beta versions regularly because things were so stable.
Anyway, that is a very subjective thing, and depends heavily on which parts of Qt you're using. Some are more stable than others.
@sierdzio I ship on Windows and macOS. Mostly I am using core desktop components + QGraphicsCanvas related classes. I find the Windows version to be pretty stable. But Qt is large and I don't know how stable the other components are. I also wish they would concentrate on stability more than new features.
-
Are other developers finding recent versions of Qt buggy on macOS, or is it just me?
I quickly wrote up some notes on my struggles to find a usable version of Qt that works on recent macOS releases:
https://successfulsoftware.net/2018/11/02/qt-is-broken-on-macos-right-now/
I thought other people might find them useful.
Here is hoping that Qt 5.12.0 is less buggy on macOS.
Hi @AndyBrice,
Here is hoping that Qt 5.12.0 is less buggy on macOS
The best way to achive that, is to try the betas (via online installer), compile your app against and report any regressions early.
I know, thats some work, but the best you can do to keep your favorite features functional.
-
@aha_1980 said in Are you finding recent Qt versions buggy on macOS?:
The best way to achive that, is to try the betas (via online installer), compile your app against and report any regressions early.
Fair comment. I am downloading 5.12.0 beta 3 for Mac as I type.
-
@aha_1980 said in Are you finding recent Qt versions buggy on macOS?:
The best way to achive that, is to try the betas (via online installer), compile your app against and report any regressions early.
Fair comment. I am downloading 5.12.0 beta 3 for Mac as I type.
Hi @AndyBrice,
The font dialog bug should have affected lots of users indeed - a painful regression.
I've got another possible solution for you - as mentionend in the bug report, you can revert one commit (or cherry-pick the fix, which is in 5.12) and compile Qt yourself. That should give you the possibility to use e.g. 5.11.2 and not to run into new problems with 5.12.
Of course it's a bit more work, and it's no excuse for these regressions, but its a possibility.
Regards
-
@aha_1980 I am shocked that the QFontDialog bug not only got through testing, in 5.11.1, but then didn't get fixed in 5.11.2!
I used to always build Qt from scratch. But that seems to have got harder over time. last time I tried I couldn't get it to build at all (might have been Windows rather than Mac).
-
@aha_1980 I am shocked that the QFontDialog bug not only got through testing, in 5.11.1, but then didn't get fixed in 5.11.2!
I used to always build Qt from scratch. But that seems to have got harder over time. last time I tried I couldn't get it to build at all (might have been Windows rather than Mac).
@AndyBrice said in Are you finding recent Qt versions buggy on macOS?:
I am shocked that the QFontDialog bug not only got through testing, in 5.11.1
I see indeed a big problem that the patch releases are not intensive tested. I guess we have more beta testers, than pre-x.1 or x.2 testers.
And even with lots of autotests, there's still something that only a human can detect.
but then didn't get fixed in 5.11.2!
My interpretion is, that they found it too risky to break something else. And I can understand this.
Qt has to stay free or it will die.
-
@AndyBrice said in Are you finding recent Qt versions buggy on macOS?:
I am shocked that the QFontDialog bug not only got through testing, in 5.11.1
I see indeed a big problem that the patch releases are not intensive tested. I guess we have more beta testers, than pre-x.1 or x.2 testers.
And even with lots of autotests, there's still something that only a human can detect.
but then didn't get fixed in 5.11.2!
My interpretion is, that they found it too risky to break something else. And I can understand this.
@aha_1980 said in Are you finding recent Qt versions buggy on macOS?:
My interpretion is, that they found it too risky to break something else. And I can understand this.
I completely understand not fixing a known minor bug, in case it breaks something else. But this bug is a showstopper for me and (surely) a high percentage of other developers.
-
@aha_1980 said in Are you finding recent Qt versions buggy on macOS?:
My interpretion is, that they found it too risky to break something else. And I can understand this.
I completely understand not fixing a known minor bug, in case it breaks something else. But this bug is a showstopper for me and (surely) a high percentage of other developers.
@AndyBrice You don't have to tell me that - I'd fully agree. Please discuss this with the developers in the corresponding bugreport.
But as said, you can fix that locally with a little effort. Therefore it is annoying, but not a showstopper.
Regards
