Jani Heikkinen

Qt 5.10 Alpha Released

Published Wednesday September 13th, 2017
30 Comments on Qt 5.10 Alpha Released
Posted in Qt, Releases

I can proudly tell that Qt 5.10 Alpha is released today.

Please check Qt 5.10 New Features -wiki to see what new is coming with Qt 5.10 release. And as usual the official Alpha is a source code delivery only.

Next milestone in our way to final Qt 5.10 release (which is planned to happen at the end of November) will be first Beta release. We are targeting to get it out soon after the Alpha. We will release several Beta releases in similar manner as we did with Qt 5.9 – made available via the online installer. Each new Beta release will add maturity and improvements based on user feedback.

Please download the Qt 5.10 Alpha source packages from your Qt Account or from download.qt.io.

Most importantly, remember to give us feedback by writing to the mailing lists and reporting bugs.



Do you like this? Share it
Share on LinkedInGoogle+Share on FacebookTweet about this on Twitter

Posted in Qt, Releases


Philippe says:

No change in QtCore? I expected QStringView to be in 5.10, as mentionned here:

Kayra says:

It seems the wiki page is not up-to-date. QStringView is in docs: http://doc-snapshots.qt.io/qt5-5.10/qstringview.html

Arixo says:

Is there something similar for QByteArray? QByteArrayView maybe?

Kayra says:

Marc Mutz improved QLatin1String substantially for 5.10 so that it has effectively become QByteArrayView for strings: http://doc-snapshots.qt.io/qt5-5.10/qlatin1string.html

A QByteArrayRef class almost made it to Qt a few years ago but it seems it’s been abandoned: https://codereview.qt-project.org/#/c/79385/ The discussions there also mention QByteArrayView since QByteArrayRef would require a QByteArray to exits in the first place which means memory allocation. However deserializing some data to into a QByteArrayRef instead of a QByteArray is a valid use case IMO. QByteArrayRef would be useful for parsing external data.

Arixo says:

Thanks for the info, that’s quite good to know.

My own use case would something like compute the CRC of a part of a network message stored in a QByteArray.
Something like ‘computeCrc(message.rightRef(messageSize – headerSize))’ if I want to compute the CRC of everything but the header.
Sure currently I can pass iterators, or just create a copy with right(), but that’d be much nicer to write.

Kayra says:

I can’t reply to your comment so I am replying to myself.

I use QByteArray::fromRawData() in cases like yours. It is more efficient than copying data but it allocates nevertheless some space for bookkeeping. QLatin1String can be used if no allocation is preferred, after all, it is a view into a char array and has ctors suitable for binary data.

@Philippe: The New Features page is expected to be fully up-to-date by the first Beta release. Some modules are not yet summarized there. Also note that the wiki page is not a full list of changes, just a few highlights.

Ntorion says:

Where can I find documentation for Qt WebGL Streaming Plugin?

Hame says:

Will there be updated installation packages in the maintenance tool (the packages are from 1st September)?

Jani Heikkinen Jani Heikkinen says:

Not with Alpha. Alpha is src delivery only. But we will update binary snapshot soon & it will be available via maintenance tool

Bartłomiej Burdukiewicz says:

Why “opensource” phrase is now missing? (“qt-everywhere-src-5.10.0-alpha.tar.xz”)

Jani Heikkinen Jani Heikkinen says:

Earlier there were some difference with opensource and enterprise src packages and that’s why there were ‘opensource’ or ‘enterprise’ in package names. From Qt 5.10 -> src packages are exactly same and that’s why names are unique as well

Krzysztof Kawa says:

Could we have a release that focuses on stability and fixing bugs instead of adding new features like crazy? I know you need to chase the ball but the last few versions feel like quantity over quality is the mantra, which is not what I like Qt for.
A one of many examples – https://bugreports.qt.io/browse/QTBUG-52108 – 4 major releases with P2 bugs in very basic functionality rots more and more and now a new feature (that has its own bugs) is added to it.

@Krzysztof: Yes, definitely. The release focusing to maturity is Qt 5.9 LTS. It is all about providing stability and performance improvements, not new features within its patch level releases. Next one is Qt 5.9.2, which we aim to get out by end of September. This does not mean the bug you pointed out is fixed there, but many other ones are. The bug you listed has priority P2, is not requested to be fixed by a commercial license holder (via Qt Support) and has only 1 vote from others.

rudi says:

I find it a strange understandig of “Quality”:
> The bug you listed has priority P2, is not requested to be fixed by a
> commercial license holder (via Qt Support) and has only 1 vote from others

while I understand it, you should be warned not to fall in the following “art of developing”:
1. fix the bugs for comercials and/or with lot of votes
2. leave all other bugs and invest the time in new features

if you do point 2. too excesively, you will crash your product one day ( may be in the far future but probably).

@rudi: We do fix other than critical bugs as well, but to get a low-priority bug fixed it helps to be a commercial license holder and have votes in the bug.

Dimi says:

How about this one?


Critical, 8 votes, untouched for 2 years despite its severity (hard crashes on occurrence). It hasn’t even been assigned to anyone…

Jean-Michaël Celerier says:

> We do fix other than critical bugs as well, but to get a low-priority bug fixed it helps to be a commercial license holder and have votes in the bug.

Is it really a good strategy ? Qt really has built a reputation of “quite buggy” over the years which has discouraged more than one to get into it. People talk about Qt bugs all the time in forums, chats, etc. I mean for instance this bug has been reported by all kinds of commercial and non-commercial users https://bugreports.qt.io/browse/QTBUG-50992 and is only being worked on recently (thank god) … or this which have been reported by gold support https://bugreports.qt.io/browse/QTBUG-54860 .

Dimi says:

P2… I’ve reported several P1 bugs, including such that lead to hard crashes, with zero work done as far back as QT 5.5… Zero work done for almost 2 years now…

A key part of being able to use Qt is to set your expectations where they should be. Don’t expect bugs to be fixed, don’t expect feature requests to be implemented. What you should expect is frequent scrapping of months of work due to hitting bugs and design limitations and having to go back, change low level design and everything on top of it, so you can work your way around the problems.

Qt is a bloated mess of redundancy and obsolescence, that stuff is hard to maintain, many bug sources are impossible to find, most design limitations are impossible to remove. The long standing tendency is for new bugs to be introduced at a much faster pace than old bugs are solved.

For better or worse, there is no better alternative to Qt, which makes it “the best” in a rather ironic way. The best you can do is limit your usage of Qt as much as possible, don’t use Qt classes directly, wrap in your own wrappers, making it easier to port it to something new eventually. Keep reinventing wheels as much as possible, wheels you have control over and don’t hold nasty surprises to be discovered when it is too late to do anything about it.

Alex says:

Sad but true, and very well said. I agree with every word.

Witek says:

Wait for such an answer:
“This task is old and has been idle for a long time. It is therefore being closed on the assumption that it will not be addressed in the foreseeable future. If you really do care about this task, you may reopen it and vote for it.”
(I’ve received such after 1.5 year of waiting, BTW. it was in reported in 2009 and it’s still not fixed, I didn’t even try to check it in the newest Qt).

Tham says:

Maybe digia should let the commercial/non-commercial users to vote what are the things they wanted most from Qt5?
Add more and more new features before fixing those critical, P1,P2 bugs or focus on bugs fix first?
I will vote for bug fix

Borgar says:

Same here!

Petya Kartoshkin says:

+1 for bug fixes

Alexey Azanov says:

+1 for bug fixes. I use the Qt version 5.6, because I can’t use the new one until the bug https://bugreports.qt.io/browse/QTBUG-47354 is fixed. Spent a lot of time fighting with bugs in Qt. Was thinking not to use qt for new development of complex software.

ivan says:

I couldn’t agree more with bug-fixes priority over new features. Just at this: https://bugreports.qt.io/browse/QTBUG-62775?filter=18739 – over five thousands (5000!) bugs that are open for more that a month and are still unresolved. Amazing.

> Digia
But it’s not Digia anymore for a couple of years already.

ivan says:

Oops, sharing a filter failed. Then just apply this query: project = Qt AND priority in (“P0: Blocker”, “P1: Critical”, “P2: Important”) AND type = Bug AND status in (Reported, Open, “In Progress”) AND resolution = Unresolved AND created < -30d ORDER BY createdDate DESC

Steve Brunton says:

What about Qt3D ? nothing new there? This module is taking forever to get to a point where it is functional to actually use it for development

ivan says:

So, the list from https://wiki.qt.io/New_Features_in_Qt_5.10 doesn’t count as “something new”?

Today says:

Hello! Any plans for Controls 2 TableView?

Commenting closed.

Get started today with Qt Download now