> On 7 May 2024, at 19:15, Thiago Macieira wrote:
>
> On Tuesday 7 May 2024 10:03:21 GMT-7 Thiago Macieira wrote:
>> So I want to know of a use-case where all of the following are true:
>> * application is GUI-less (i.e., is a background service)
>> * application has no GUI counterpart
>> * app
> On 6 May 2024, at 09:02, Marc Mutz via Development
> wrote:
>
> Hi,
>
> Juha is currently improving the OAuth implementation in QtNetworkAuth.
> The protocol involves launching the system browser to get an access
> code, in turn used to get access tokens with which services can then be
>
+1!
Lars
> On 14 Mar 2024, at 10:06, Tor Arne Vestbø via Development
> wrote:
>
> Hi,
>
> I would like to nominate Jøger Hansegård for approver rights in the Qt
> project.
>
> Jøger joined The Qt Company 10 months ago and has since then been getting his
> hands dirty in Qt Multimedia, and
> On 22 Dec 2023, at 17:48, Giuseppe D'Angelo via Development
> wrote:
>
> Il 22/12/23 17:08, Pierre-Yves Siret ha scritto:
>> I wouldn't want a radii grouped property just because of its name.
>> I much prefer writing topLeftRadius: 10 than radii.topLeft: 10.
>> The pedantic latin syntax doesn'
> On 22 Dec 2023, at 13:54, Tor Arne Vestbø via Development
> wrote:
>
>> On 22 Dec 2023, at 13:20, Giuseppe D'Angelo via Development
>> wrote:
>>
>> Il 22/12/23 11:15, André Somers ha scritto:
>>> I can see two options. The simplest option is to have a `radii`
>>> property, which is a group
> On 24 Aug 2023, at 14:30, Giuseppe D'Angelo via Development
> wrote:
>
> On 22/08/2023 23:27, Marc Mutz via Development wrote:
>> We have
>> https://community.kde.org/Policies/Binary_Compatibility_Issues_With_C%2B%2B
>> for backwards binary compatibility issues and we have
>> https://contri
> On 23 Aug 2023, at 11:48, Edward Welbourne via Development
> wrote:
>
> On Tuesday, 22 August 2023 14:27:09 PDT Marc Mutz via Development wrote:
I think we should decide what we mean by forward BC and SC and
describe it in https://wiki.qt.io/Qt-Version-Compatibility more
preci
Hi all,
I’d like to nominate Artem Dyomin for approver rights in Qt.
Artem has been working with Qt Multimedia since last summer, doing a very good
job implementing new features, fixing bugs and refactoring code in the module.
You can see his merged changes here:
https://codereview.qt-project.
+1
He’s been doing that job without the title for years already :)
Cheers,
Lars
> On 4 May 2023, at 12:10, Marc Mutz via Development
> wrote:
>
> Hi,
>
> I'd like to nominate Eddy as the maintainer for the QLocale and
> src/corelib/time QtCore subsystems. Eddy is filling that role de-facto
> On 17 Apr 2023, at 18:16, Thiago Macieira wrote:
>
> On Monday, 20 March 2023 08:44:30 CDT Edward Welbourne wrote:
>> Thiago Macieira (31 October 2019 22:11) wrote [0]:
>>> This RFC (...) is meant to discuss how we'll deal with locales on Unix
>>> systems on Qt 6. This does not apply to Windo
Hi,
> On 21 Mar 2023, at 17:46, Alvin Wong via Development
> wrote:
>
> Hi,
>
> Yes, embedding the manifest with activeCodePage set to UTF-8 is the only
> thing need to enable UTF-8 as the ANSI code page (ACP) for the process.
>
> Qt itself should work fine after the bug in QStringConverter
I agree. Let’s change behaviour and move it to active after a call to resume().
It also behaves the same in push and pull mode in that case.
Cheers,
Lars
> On 31 Jan 2023, at 13:11, Tor Arne Vestbø via Development
> wrote:
>
> Hi,
>
> This does indeed look like an oversight, where the behavi
> On 16 Sep 2022, at 03:36, Chris Adams wrote:
>
> Hi Gaurav,
>
> First, I want to make clear: I know nothing about printing at all,
> either in Qt or in general.
> But I did a quick archive search and found the following:
> https://lists.qt-project.org/pipermail/development/2020-May/039584.htm
Hi Eddy,
On 20 Jul 2022, at 16:50, Edward Welbourne
mailto:edward.welbou...@qt.io>> wrote:
Hi all,
TL;DR: there's a new [[Deprecation]] wiki page, please review.
We noticed recently that some APIs had been wrapped in #if-ery on
QT_DEPRECATED_SINCE(major, minor) without having QT_DEPRECATED or
Hi everbody,
The voting period for the new Chief Maintainer has ended yesterday. I’m really
happy to say that we have elected a new Chief Maintainer.
Before getting to the results, I’d like to thank both candidates for stepping
up and their willingness to take over the role.
The vote ended wit
+1.
Lars
> On 13 Jun 2022, at 09:19, Frederik Gladhorn wrote:
>
> Hello :)
>
> I've lately not had time to contribute to Qt (personal life keeping me busy).
> Since Volker and others did a great job porting Qt Speech to Qt 6, they know
> the code better than me by this time. I'd like to step
Hi,
Just a short reminder for all Maintainers:
In case you haven’t voted for a new Chief Maintainer, you can still do so until
end of Thursday.
Cheers,
Lars
On 2 Jun 2022, at 11:46, Lars Knoll mailto:lars.kn...@qt.io>>
wrote:
Hi all,
The nomination period for the Qt Chief Main
> On 9 Jun 2022, at 19:16, Alexander Akulich wrote:
>
> Hi everyone,
>
> On Wed, Jun 8, 2022 at 5:18 PM Fabian Kosmale wrote:
>>
>> What remains to be done:
>> - There are concerns that mixing Qt versions might lead to an unbounded
>> memory leak with the current implementation.
>
> I can
I think that’s ok given that its self contained, and something users really
need on mobile. But as with the other exception, please try to finish it as
soon as possible.
Cheers,
Lars
On 9 Jun 2022, at 15:01, Tor Arne Vestbø
mailto:tor.arne.ves...@qt.io>> wrote:
Hi,
The permission API (https:
Given that the change doesn’t interfere with existing functionality, this is
ok. But please try to finish and get the change merged as soon as possible.
Cheers,
Lars
> On 8 Jun 2022, at 16:17, Fabian Kosmale wrote:
>
> Hi,
>
> unfortunately, we did not manage to get a QStringConverter backend
Hi all,
The nomination period for the Qt Chief Maintainer election ended yesterday
night.
I’m very happy to say that we have two excellent candidates for the position
with Allan and Volker. Both have been working with Qt for many years and know
it extremely well. I am certain that whoever of t
2022 at 0:00 CEST and
end on Thursday the 16th of June 2022 at 23:59 CEST.
Cheers,
Lars
> On 20 May 2022, at 11:07, Lars Knoll wrote:
>
> Hi everybody,
>
> Sorry for being a bit slow to answer, the last days were a bit hectic for me
> :)
>
> As I’m for the moment still
t;
> The road has seen some bumps but your teams and you have managed to keep Qt
> moving forward in interesting ways through all these years.
>
> It has been a pleasure to work with you on some of my contributions.
>
> All the best for your new journey !
>
> Samuel
&g
Hi everybody,
Sorry for being a bit slow to answer, the last days were a bit hectic for me :)
As I’m for the moment still the Chief Maintainer, I guess it’s also my
responsibility to get the nomination and voting process organised.
I do agree that we will need a full vote of all maintainers, es
Hi all,
As I’ve said in my other email, I am resigning from my position at The Qt
Company to join a small startup in Norway that is working with things unrelated
to Qt.
As such, I won’t have too much time to spend with Qt in the future anymore, and
will resign from my position as the Chief Mai
Hi all,
Let’s take the big news first. I’ve resigned from my position at The Qt
Company. More on that and what it means for the Qt Project further below.
But as I’ve spent almost exactly 25 years in the Qt ecosystem, 22 of those
working for the various companies owning Qt, I hope it’s ok if this
Hi Tomi,
> On 19 Apr 2022, at 21:49, Tomi Pannila wrote:
>
> Hi Qt developers,
>
> could you please explain how your method "QRect::contains(const QRect &r,
> bool proper)" at
> https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/tools/qrect.cpp?h=dev
> satisfies your API design principles
+1.
Lars
On 14 Mar 2022, at 08:53, Eskil Abrahamsen Blomfeldt
mailto:eskil.abrahamsen-blomfe...@qt.io>>
wrote:
Hi,
We are working on an integration of - and API for using - the PhysX physics
engine with Qt Quick 3D. We would like to request a qt/ repository for
including this as a supported
Done. Maintainer approval based on the +1 from Alexandru :)
> On 10 Mar 2022, at 04:01, Thiago Macieira wrote:
>
> It's been 23 days since I last uploaded the patch. There are two +1 votes
> within 2 days of the upload, but no action since then.
>
> This is not QtCore, so I don't feel right in
Done.
Lars
> On 8 Mar 2022, at 05:51, Thiago Macieira wrote:
>
> https://codereview.qt-project.org/q/Ib056b47dde3341ef9a5213ef677e471674b6
>
> I'll abandon anything not approved in one week.
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
> Software Architect - Intel DPG Cloud
> On 16 Feb 2022, at 18:10, Thiago Macieira wrote:
>
> On Tuesday, 15 February 2022 07:54:07 PST Marc Mutz wrote:
>> https://bugreports.qt.io/browse/QTBUG-100845
>>
>> The QWaylandBufferRef class has a very annoying bug in that its relational
>> operators cannot compare `const` objects (only on
Hi Marc,
Two questions:
* Is there a work-around for the developers with the current state, e.g. by
adding some casts?
* Could you add the missing operators inline, so they don’t add new symbols?
Cheers,
Lars
On 15 Feb 2022, at 16:54, Marc Mutz mailto:marc.m...@qt.io>>
wrote:
Hi,
https://bu
+1.
Cheers,
Lars
On 1 Feb 2022, at 10:50, Gatis Paeglis
mailto:gatis.paeg...@qt.io>> wrote:
Hi all,
I would like to propose a change in Qt's Linux/XCB maintainership.
Since 2019, I have moved full time to the Qt for MCUs project and
there is no time left for XCB work.
/qtbase/src/plugins/plat
> On 28 Jan 2022, at 02:07, Thiago Macieira wrote:
>
> On Thursday, 27 January 2022 16:49:22 PST Marc Mutz wrote:
>> That would break projects that build their Qt themselves (embedded), and
>> with C++17 (because, you know, compile times increase with every std
>> version 🙂).
>
> Ok, then we ma
+1!
Cheers,
Lars
> On 25 Jan 2022, at 09:46, Fabian Kosmale wrote:
>
> +1
>
> Volker has been doing a great job fixing issues, stabilizing tests and
> improving the unit test coverage in the Widgets module
>
>
> Von: Development im Auftrag von Richar
+1.
Lars
On 20 Jan 2022, at 07:31, Jukka Jokiniva
mailto:jukka.jokin...@qt.io>> wrote:
+1 from me too
--Jukka
From: Development
mailto:development-boun...@qt-project.org>>
on behalf of Oliver Eftevaag
mailto:oliver.eftev...@qt.io>>
Date: Wednesday, 19. January 2022 at 16.01
To: Mårten
Hi Thiago,
I’m absolutely in favour of upping the SIMD support in Qt. Compilers support
everything we need, and we should make better use of that.
The main thing I’m wondering about is how much performance we gain by from a
multi arch build Qt for different x86_64 architectures opposed to build
Another +1.
Thanks for stepping up, Sona!
Cheers,
Lars
> On 18 Jan 2022, at 16:36, Mårten Nordheim wrote:
>
> +1 from me as well
>
>
> From: Development on behalf of Cristián
> Maureira-Fredes
> Sent: Tuesday, January 18, 2022 15:10
> To: developme
> On 3 Jan 2022, at 16:10, Sérgio Martins wrote:
>
> On 2022-01-03 13:40, Lars Knoll wrote:
>> (...)
>> One other possible solution to improve compile times is the hack we
>> used 15 years ago in KDE, where we grouped many .cpp files into one
>> compilatio
On 3 Jan 2022, at 14:21, Thiago Macieira
mailto:thiago.macie...@intel.com>> wrote:
On Monday, 3 January 2022 05:43:53 -03 Marc Mutz wrote:
Hi,
The Qt Creator folks have noted that compilation of Qt projects against Qt
6.2 is sometimes almost twice as slow as it was in 5.15:
https://bugreports.
I guess qtdeclarative already has one exception, so this would make it two.
The exception is fine for me, as this shouldn’t effect anything outside of
qtdeclarative. But please to to get it finished this week.
Cheers,
Lars
On 13 Dec 2021, at 11:37, Andrei Golubev
mailto:andrei.golu...@qt.io>>
Hi Alberto,
> On 12 Dec 2021, at 08:03, Alberto Mardegan
> wrote:
>
> Hi all!
> When the new QtMultimedia was announced [1], there was a mention that
> the Radio API was being removed (by the way, there is no mention of this
> removal in the migration document [2]). Did it happen because of a
>> -Original Message-
>> From: Fabian Kosmale
>> Sent: perjantai 10. joulukuuta 2021 10.47
>> To: Lars Knoll
>> Cc: Qt development mailing list ; Jani
>> Heikkinen
>> Subject: AW: [Development] Feature freeze exception for QML Language
>&g
As far as I can see, qtlanguageserver is not currently being packaged or part
of the release. So we’d need to be adding that module in addition to the
feature freeze exception for declarative.
Jani, what do you think? Would you expect any problems/delays adding the
qtlanguageserver repository (
> On 9 Dec 2021, at 09:57, Alexandru Croitor wrote:
>
>
>> On 9. Dec 2021, at 08:53, Lars Knoll wrote:
>>
>> I’m always a bit worried about build system changes in stable branches. Does
>> this in any way interfere with or change how Qt itself is bein
I’m always a bit worried about build system changes in stable branches. Does
this in any way interfere with or change how Qt itself is being build and
packaged?
Cheers,
Lars
> On 7 Dec 2021, at 12:21, Alexandru Croitor wrote:
>
> Hi,
>
> I'd like to request a feature freeze exception for add
2021, at 09:53, Lars Knoll
mailto:lars.kn...@qt.io>> wrote:
Hi all,
The vote has been closed on Tuesday night. 33 Approvers voted, 24 in favour of
the no confidence vote, 9 against. This means that the no-confidence vote
passed the required quorum of 2/3 of the votes as defined in QUIP-2
+1 from my side. If nothing has happened to the task for 3 months, it’s very
likely there’s no progress.
Cheers,
Lars
> On 28 Oct 2021, at 15:44, Alex Blasche wrote:
>
> Hi,
>
> We have a growing problem with Jira issues forgotten in the "In Progress"
> state. For the 10 most important Jira
-plantation false
nimble-tablefalse
fluffy-window false
wakeful-cracker false
On 19 Oct 2021, at 09:57, Lars Knoll
mailto:lars.kn...@qt.io>> wrote:
Hi all,
We had a request for a vote of no confidence against Oswald Buddenhagen by Ivan
Komissarov some weeks ago (*). Such a vote
I’ve worked with her a lot on the new Qt Multimedia module for Qt 6 and
completely agree with Volker.
So +1 from my side :)
Cheers,
Lars
> On 27 Oct 2021, at 11:56, Volker Hilsheimer wrote:
>
> Hello World,
>
> I’d like to nominate Doris Verria as approver in the Qt Project.
>
> Doris has
On 19 Oct 2021, at 20:56, Oswald Buddenhagen
mailto:oswald.buddenha...@gmx.de>> wrote:
hello jury,
On Tue, Oct 19, 2021 at 07:57:39AM +, Lars Knoll wrote:
I’d like to urge everybody who is going to cast a vote to [...]
as lars' mail sadly doesn't provide any actual guida
> On 19 Oct 2021, at 09:57, Lars Knoll wrote:
>
>
> Hi all,
>
> We had a request for a vote of no confidence against Oswald Buddenhagen by
> Ivan Komissarov some weeks ago (*). Such a vote can be asked for by another
> Approver according to our governance model (**
Hi all,
We had a request for a vote of no confidence against Oswald Buddenhagen by Ivan
Komissarov some weeks ago (*). Such a vote can be asked for by another Approver
according to our governance model (**).
As this was the first time this passus got invoked, we had to do some work to
put a
> On 7 Oct 2021, at 10:52, Edward Welbourne wrote:
>
> Lars Knoll (6 October 2021 15:33) wrote:
>> * voting will be open for 7 days to give everybody enough time to react
>> * The voting database will be deleted 2 weeks after voting ended
>
> Suggested revision
items that I propose to add:
* voting will be open for 7 days to give everybody enough time to react
* The voting database will be deleted 2 weeks after voting ended
Cheers,
Lars
> On 1 Oct 2021, at 19:43, Lars Knoll wrote:
>
> Hi all,
>
> As you might have seen, we had a reque
Hi all,
As you might have seen, we had a request for a formal vote of no confidence on
an Approver status according to the last paragraph in QUIP-2/How to become an
Approver(*) in the recent QBS thread(**).
This is the first time we will need such a formal vote, which also means that
we so far
Hi all,
Just wanted to give a quick heads-up that this hasn’t been forgotten. But I’ve
been sick with the flu the last week and simply didn’t manage to push things
forward.
As we have so far not had the need for such a vote, there’s some things we’ll
need to sort out to make it happen. I’ll fo
Hi,
I think this discussion about details is pretty much irrelevant.
The original problem is that using a -2 to block a change that has been
approved by the module maintainer is basically abusing gerrit to break our
governance model. QUIP-2 clearly states that the maintainer has decision power
Yours,
Tuukka
From: Development
mailto:development-boun...@qt-project.org>>
on behalf of Иван Комиссаров mailto:abba...@gmail.com>>
Date: Tuesday, 14. September 2021 at 20.49
To: Lars Knoll mailto:lars.kn...@qt.io>>
Cc: Qt development mailing list
mailto:development@qt-p
Hi,
Let’s also take up the formal part of the request.
On 13 Sep 2021, at 22:59, Иван Комиссаров
mailto:abba...@gmail.com>> wrote:
Also, some actions might be taken to prevent from happening in the future - if
technically possible, I’d like to request the revoke of his approver rights on
the Q
> On 14 Sep 2021, at 12:34, Richard Weickelt wrote:
>
>
>> Just for the sake of clarity, who *is* the Maintainer of QBS ?
>> Our wiki's [[Maintainers]] page only mentions Christian Kandeler as
>> maintainer of Qt Creator's integration with it. I gather Ivan is a/the
>> principal developer of QB
Another +1 from my side.
Cheers,
Lars
> On 5 Aug 2021, at 13:29, Andy Nichols wrote:
>
> +1 from me as well. Managed to miss this nomination while I was on vacation,
> but Kaj has been making excellent contributions to the Qt Graphics stack for
> multiple years and I think approver status in
> On 27 Jul 2021, at 07:19, Jani Heikkinen wrote:
>
>> -Original Message-
>> From: Mitch Curtis
>> Sent: perjantai 23. heinäkuuta 2021 17.12
>> To: Alexandru Croitor
>> Cc: development@qt-project.org; Qt Releases
>> Subject: Re: [Development] Temporarily preventing changes being staged
Another +1.
Cheers,
Lars
> On 28 Jun 2021, at 15:24, Ulf Hermann wrote:
>
> +1
>
> On 6/28/21 12:51 PM, Cristián Maureira-Fredes wrote:
>> Hello everyone,
>> Context
>> ---
>> After the "Improve the contributor experience" session at the past Qt
>> Contributors Summit, many ideas came out
Another +1 and a big thanks to Friedemann for his work on the Windows port over
all the years!
Cheers,
Lars
> On 16 Jun 2021, at 11:18, Morten Sørvig wrote:
>
> +1 from me as well, and I’d like to thank Friedemann for his work on Qt on
> Windows through the years.
>
> Morten
>
>> On 15 Jun
Hi all,
This is a short reminder that feature freeze for 6.2 is coming up tomorrow
evening. There is still time over the weekend to merge pending changes that
didn’t make it until Friday evening, but those days should only be used to
merge changes that are already approved but still pending on
Of course. The +1 only applies to Qt 6, and not any versions of Qt 5 :)
Cheers,
Lars
> On 1 Jun 2021, at 14:58, David Skoland wrote:
>
> To be clear: +1 to changing default behavior in 6.2.
>
>> On 1 Jun 2021, at 14:57, David Skoland wrote:
>>
>> Not thrilled about subtle default behavior ch
On 28 May 2021, at 16:37, Konstantin Shegunov
mailto:kshegu...@gmail.com>> wrote:
On Fri, May 28, 2021 at 2:13 PM Volker Hilsheimer
mailto:volker.hilshei...@qt.io>> wrote:
Hey Widget fans,
Hola,
I need your opinions on https://bugreports.qt.io/browse/QTBUG-59888
The UX resulting from our (str
Thanks a lot for this, Peppe!
Btw, do you know is there’s a policy with regards to nicknames one had
registered on Freenode? Just wondering as someone registered my old nick on
Libera.
Cheers,
Lars
> On 29 May 2021, at 19:27, Elvis Stansvik wrote:
>
> Thanks for taking care of this Peppe.
>
> On 28 May 2021, at 10:27, Samuel Gaist wrote:
>
>
>> On 28 May 2021, at 10:09, Lars Knoll wrote:
>>
>>> On 28 May 2021, at 09:15, Alberto Mardegan
>>> wrote:
>>>
>>> Hi Lars,
>>>
>>> On 26/05/21 15:09, Lars K
> On 28 May 2021, at 09:15, Alberto Mardegan
> wrote:
>
> Hi Lars,
>
> On 26/05/21 15:09, Lars Knoll wrote:
>> The hope is that we can change that for Qt 6. To make this possible, we have
>> changed not only parts of the public API, but completely redone
On 27 May 2021, at 16:18, Lars Knoll
mailto:lars.kn...@qt.io>> wrote:
On 27 May 2021, at 15:34, Eike Hein mailto:h...@kde.org>> wrote:
May 27, 2021 2:51 PM, "Samuel Gaist"
mailto:samuel.ga...@idiap.ch>> wrote:
I think one of the main use case I have seen for custo
> On 27 May 2021, at 15:34, Eike Hein wrote:
>
> May 27, 2021 2:51 PM, "Samuel Gaist" wrote:
>> I think one of the main use case I have seen for custom GStreamer pipelines
>> is to be able to get
>> rtsp or other network streams in Qt applications.
>
> This is my personal use case as well.
> On 27 May 2021, at 14:35, Lars Knoll
> mailto:lars.kn...@qt.io>> wrote:
>
>> On 27 May 2021, at 14:25, Eike Hein mailto:h...@kde.org>>
>> wrote:
>>
>> May 27, 2021 8:14 AM, "Lars Knoll"
>> mailto:lars.kn...@qt.io>> wrote:
>&
> On 27 May 2021, at 14:25, Eike Hein wrote:
>
> May 27, 2021 8:14 AM, "Lars Knoll" wrote:
>> The one thing I want to avoid is what we had in Qt 5, where you could force
>> Qt MM to use a
>> different/custom gstreamer pipeline based on environment variable
> On 26 May 2021, at 17:30, Eike Hein wrote:
>
> Exciting!
>
> Are there any plans to officially support the GStreamer backend on Android
> down the line (with building GStreamer as an acceptable exercise left to the
> user) or would work in that direction be appreciated by the module mainta
On 26 May 2021, at 21:00, Arnaud Vrac
mailto:raw...@gmail.com>> wrote:
Le mer. 26 mai 2021 à 14:11, Lars Knoll
mailto:lars.kn...@qt.io>> a écrit :
[snip]
Hi Lars,
Thanks for the updates. One feature that I've always waited for is the
possibility to list and select audio/sub
> On 26 May 2021, at 18:14, Jason H wrote:
>
>>> 4. On the removal of QAbstractVideoFilter AND QVideoProbe: Disappointed to
>>> hear this. I previously used this for read-only frames for analysis, i.e.
>>> Barcode reading and object detection. How do we do that now?
>>
>> You can get full acc
> On 26 May 2021, at 16:47, Alexander Akulich
> wrote:
>
> On Wed, May 26, 2021 at 5:25 PM Jason H wrote:
>>
>> 4. On the removal of QAbstractVideoFilter AND QVideoProbe: Disappointed to
>> hear this. I previously used this for read-only frames for analysis, i.e.
>> Barcode reading and obje
> On 26 May 2021, at 16:24, Jason H wrote:
>
>> There are still open issues and gaps in the implementation that need fixing,
>> but the code is now in a decent enough shape to merge it back to dev and
>> continue on that branch. We will however now have everything ready in Qt
>> Multimedia fo
> On 26 May 2021, at 14:09, Lars Knoll wrote:
[snip]
> There are still open issues and gaps in the implementation that need fixing,
> but the code is now in a decent enough shape to merge it back to dev and
> continue on that branch. We will however now have everything ready in Qt
Hi all,
After 5 months of work, I am now preparing to merge the new API and
implementation for Qt Multimedia back into the development branch.
You can find the first iteration of a merge commit here:
https://codereview.qt-project.org/c/qt/qtmultimedia/+/351108
With this, Qt Multimedia is proba
Another +1. All reviews of my patches that Andreas has done have been really
good and thorough :)
Cheers,
Lars
On 29 Apr 2021, at 08:44, Andrei Golubev
mailto:andrei.golu...@qt.io>> wrote:
+1.
Indeed, Andreas does a great job daily.
--
Best Regards,
Andrei
Fr
Hi Brett,
The binary JSON support is deprecated and only there for backwards
compatibility. It had some issues (e.g. it couldn’t handle large JSON files),
that’s why we deprecated it. It’s gone in Qt 6. I guess the docs need some
adjustment though.
Cheers,
Lars
On 13 Apr 2021, at 15:43, Stott
Hi all,
As you all know, we’ve been doing a lot of work for Qt 6.0 to bring the concept
of property bindings into Qt Core and make it accessible from C++
(https://www.qt.io/blog/property-bindings-in-qt-6). Unfortunately, we lacked
the time to do extensive porting of existing properties to the n
> On 27 Mar 2021, at 11:23, Giuseppe D'Angelo via Development
> wrote:
>
> Hi,
>
> On 12/03/2021 17:22, Tor Arne Vestbø wrote:
>> We we please improve this by:
>> 1. Attempt to cherry-pick the commits in the tested branch into dev, before
>> falling back to a merge commit (if needed)
>> 2.
On 5 Mar 2021, at 12:08, Tor Arne Vestbø
mailto:tor.arne.ves...@qt.io>> wrote:
On 3 Mar 2021, at 16:53, Andrei Golubev
mailto:andrei.golu...@qt.io>> wrote:
QString hello = u"Hello"; // oops, compilation error
This seems like a bug though? From an API point of view, I’d expect this simple
ass
Hi all,
While the CI maintenance break today took a little longer than usual, it also
came with two very nice new features that will hopefully make everybody’s life
easier.
First of all, you can now find a ‘Precheck' button in gerrit. That button
triggers a full CI test run of the Sha1 in the
Ok, as long as they have a low risk of breaking modules depending on qtbase :)
Cheers,
Lars
> On 1 Feb 2021, at 14:27, Giuseppe D'Angelo wrote:
>
> Il 01/02/21 14:03, Lars Knoll ha scritto:
>> Do you have a list of pending features that you think should still go into
&
Hi Guiseppe,
> On 1 Feb 2021, at 13:48, Giuseppe D'Angelo via Development
> wrote:
>
> Il 01/02/21 13:34, Jani Heikkinen ha scritto:
>> Qt 6.1 Feature Freeze is in effect now. So please do not add any new
>> features, API changes ect in 'dev' anymore until we have done branching from
>> 'dev'
> On 21 Jan 2021, at 11:14, Edward Welbourne wrote:
>
> Karsten Heimrich (21 January 2021 10:49) wrote:
>> [...] I would like to propose/request to rename the module to
>> qtstatemachine to reflect the widened code base. Jira task:
>> QTBUG-89837
>
> Sounds like a more accessible name to me - I
+1
Cheers,
Lars
> On 14 Dec 2020, at 11:21, Cristián Maureira-Fredes
> wrote:
>
> +1
>
> Additionally:
> Max managed to solve many issues on the Python+QML integration for Qt6.
>
> Cheers
>
> On 12/14/20 9:13 AM, Ulf Hermann wrote:
>> Hi,
>> I would like to nominate Max Goldstein as an appr
> On 9 Dec 2020, at 21:34, Thiago Macieira wrote:
>
> They've finally fixed the thread_local problem
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83562
>
> So when can we require a fixed version of GCC or require Clang for MinGW?
Good question. Is there a chance to move over to one of those
> On 9 Dec 2020, at 18:49, Thiago Macieira wrote:
>
> On Wednesday, 9 December 2020 02:00:29 PST Benjamin TERRIER wrote:
>> Back to the topic, wouldn't it be acceptable to break BC before 6.2 release?
>> I mean Qt 6 isn't really complete until 6.2, so if a break is required it
>> kind of makes se
Hi all,
First of all, I wanted to thank everybody for the hard work towards getting Qt
6.0 out of the door. We now have a first RC out, so we’re definitely getting
very close to the 6.0.0 release.
With that and the fact that we now have a 6.0 branch, it’s also time to start
looking a bit ahead
> On 23 Nov 2020, at 09:57, Giuseppe D'Angelo via Development
> wrote:
>
> Hi,
>
> On 22/09/2020 16:17, Thiago Macieira wrote:
>> And especially if there's no impact to how the user uses the API.
>>> 1)
>>> std::optional compare();
>>>
>>> 2)
>>> enum class Ordering { Less = -1, Equal = 0, Gre
On 18 Nov 2020, at 00:41, Lisandro Damián Nicanor Pérez Meyer
mailto:perezme...@gmail.com>> wrote:
On Tue, 17 Nov 2020 at 14:09, Thiago Macieira
mailto:thiago.macie...@intel.com>> wrote:
On Tuesday, 27 October 2020 09:34:44 PST Thiago Macieira wrote:
Have we fixed it?
I do not plan on updati
> On 13 Nov 2020, at 18:49, Thiago Macieira wrote:
>
> On Friday, 13 November 2020 00:19:41 PST Lars Knoll wrote:
>> I would hope that we’ll get mechanism to move them and help from the
>> compiler and/or C++ standard here. This is especially needed for
>> relocatab
> On 13 Nov 2020, at 09:06, Thiago Macieira wrote:
>
> On Thursday, 12 November 2020 23:45:35 PST Lars Knoll wrote:
>> Huh? In a release build assertions also expand to nothing. So it does remove
>> many checks. Opposed to that, a debug build or one with address sanitiser
&g
> On 13 Nov 2020, at 07:48, Thiago Macieira wrote:
>
> On Thursday, 12 November 2020 07:07:53 PST Lars Knoll wrote:
>> So except for the memset(0) for default construction, Primitive and Trivial
>> have the same conditions in your list here. My proposal would be to
1 - 100 of 529 matches
Mail list logo
