_______
>> From: Jaroslaw Kobus
>> Sent: Monday, June 30, 2025 7:30 AM
>> To: Volker Hilsheimer
>> Cc: Qt Development
>> Subject: Re: Requesting a repository for Qt Tasking
>>
>>
>> Hi Volker,
>>
>> the
> On 10 Jul 2025, at 14:37, Marc Mutz via Development
> wrote:
>
> Hi,
>
> I'm coming back to this thread, because this conclusion:
>
>
> Confidential
> On 18.03.24 16:28, Volker Hilsheimer wrote:
> [...]
>>
>> to use those APIs you have
> On 24 Jun 2025, at 07:56, Sze Howe Koh wrote:
>
> A few years ago, our private headers were updated to include
> qglobal_p.h. Examples:
> * https://codereview.qt-project.org/c/qt/qtbase/+/121135
> * https://codereview.qt-project.org/c/qt/qtdeclarative/+/395249
>
> The commit messages say, "See
> On 18 Jun 2025, at 10:09, Marc Mutz via Development
> wrote:
>
> I went though all of them (not the QML ones, for which I'm not
> qualified) at least once.
>
> Most have comments, I approved only 10. All maintainers, please check
> whether your module has comments as soon as possible.
>
> An
> On 5 Jun 2025, at 17:39, Volker Hilsheimer via Development
> wrote:
>
>> On 5 Jun 2025, at 13:34, Artem Dyomin via Development
>> wrote:
>>
>> Hi!
>>
>> The QtMultimedia team had implemented and approved some window capture
>> enhance
> On 5 Jun 2025, at 13:34, Artem Dyomin via Development
> wrote:
>
> Hi!
>
> The QtMultimedia team had implemented and approved some window capture
> enhancements before the feature freeze started.
>
> The relation chain
> https://codereview.qt-project.org/c/qt/qtmultimedia/+/648386
> https:/
> On 2 Jun 2025, at 09:32, Volker Hilsheimer via Development
> wrote:
>
>> On 31 May 2025, at 02:14, Hamed Masafi wrote:
>>
>> Hi
>>
>> Sorry, I forgot to share the link
>> https://codereview.qt-project.org/c/qt/qtdeclarative/+/648149
>>
>
Approved, go ahead and cherry-pick to 6.10.
Cheers,
Volker
> On 2 Jun 2025, at 09:41, Volker Hilsheimer via Development
> wrote:
>
> Hi Sami,
>
> Keep staging it so that we know that it works in dev; as mentioned just now
> in reply to Hamed, we’ll review and decide
> On 2 Jun 2025, at 10:08, Eskil Abrahamsen Blomfeldt via Development
> wrote:
>
> Hi,
>
> A new lottietoqml tool was ready to go (as tech preview) last week, but it
> needs a dependency update before we can actually merge it. The last
> successful update was May 23rd. It also introduces a
> On 2 Jun 2025, at 11:13, Tor Arne Vestbø via Development
> wrote:
>
> Hi,
>
> For 6.10 we wanted to make the iOS style in Qt Quick controls enable expanded
> client areas (added in 6.9), but the change didn’t integrate over the weekend
> due to tests making assumptions about where it cou
Hi Sami,
Keep staging it so that we know that it works in dev; as mentioned just now in
reply to Hamed, we’ll review and decide on exception requests in the release
team meeting.
If you get an exception, you’ll have to manually cherry-pick the change:
https://wiki.qt.io/Branch_Guidelines#How_t
> On 31 May 2025, at 02:14, Hamed Masafi wrote:
>
> Hi
>
> Sorry, I forgot to share the link
> https://codereview.qt-project.org/c/qt/qtdeclarative/+/648149
>
> Hamed
Thanks for working on this, Hamed! We’ll discuss Feature Freeze exceptions
tomorrow in the release team meeting on (#qt-rel
This merged in time for the branching, so no need or that exception. Just
update whatsnew610.qdoc, please :)
Volker
> On 30 May 2025, at 14:32, Jan-Arve Sæther via Development
> wrote:
>
> We’d like to ask for Feature Freeze exception for SearchField
> https://codereview.qt-project.org/c/qt
Hi,
I would like to nominate Michael Weghorn as an approver for the Qt project.
Michael has for several years been an active contributor of new feature and
improvements, in particular to Qt’s accessibility support and platform
integrations. He gives good feedback in reviews, and some of us met
> On 26 May 2025, at 15:56, Jaroslaw Kobus via Development
> wrote:
>
> Hi All,
>
> I'd like to start a broader discussion about including TaskTree in Qt and
> making it a public API.
>
> TaskTree is a solution broadly used in QtCreator in hundreds of places,
> for convenient managing of sets
> On 21 May 2025, at 08:47, Volker Hilsheimer via Development
> wrote:
>
>
>
>> On 20 May 2025, at 12:50, Giuseppe D'Angelo
>> wrote:
>>
>> On 20/05/2025 10:26, Richard Gustavsen wrote:
>>> Would it be more convenient to put th
Hi,
The change that adds the whatsnew610.qdoc file at
https://codereview.qt-project.org/c/qt/qtdoc/+/642364 is still open for
in-gerrit editing. There is so far very little to show, so if you landed
anything, please add a quick note by Friday.
Cheers,
Volker
PS: Indeed, QGenericItemModel isn’
> On 20 May 2025, at 12:50, Giuseppe D'Angelo wrote:
>
> On 20/05/2025 10:26, Richard Gustavsen wrote:
>> Would it be more convenient to put the range API directly on QRangeModel
>> instead? E.g:
>> QRangeModel model({1, 2, 3, 4, 5});
>> listView.setModel(&model);
>> model.erase(model.begin())
> On 12 May 2025, at 13:29, Kevin Kofler via Development
> wrote:
>
> Volker Hilsheimer via Development wrote:
>> I suspect that “Adaptor” will be a good term to use for such a class.
>
> Is this not more commonly spelled "Adapter"?
>
>Kevi
There are several reasons we didn’t include QtGamepad in Qt 6 so far:
- does it have enough users to justify the work to keep it alive?
- is the design/architecture up to modern Qt 6 standards?
- are there things we want to do to support a broader use case?
- does anyone want to maintain it?
I ha
> On 12 May 2025, at 10:41, Giuseppe D'Angelo wrote:
>
> On 12/05/2025 09:53, Volker Hilsheimer wrote:
>> Would a simple
>> QRangeItemModel
>> be clear enough? The “Based” doesn’t seem to add a lot of clarity.
>
> It does what it says, thou
> On 10 May 2025, at 11:37, Giuseppe D'Angelo via Development
> wrote:
>
> Il 09/05/25 17:26, Edward Welbourne ha scritto:
>>> The only issue I have is with the name.
>> QRangeAdaptorItemModel ?
>> Just reading your words back at you ...
>
> Well, maybe the authors of the class wanted to defend
> On 9 May 2025, at 15:01, Giuseppe D'Angelo via Development
> wrote:
>
> Hi,
>
> QGenericItemModel is a new API (TP?) in 6.10:
> https://doc-snapshots.qt.io/qt6-dev/qgenericitemmodel.html
>
> In a nutshell, it's an adaptor that wraps a range and exposes it through the
> QAIM API. This allows
> On 28 Apr 2025, at 13:41, Jani Heikkinen via Development
> wrote:
>
> Hi all,
> Just a kindly reminder: the Qt 6.10 Feature freeze will be in effect May
> 30th and the Qt 6.10 platform and module freeze already May 16th,
> seehttps://wiki.qt.io/Qt_6.10_Release.
> So It is time to start
Passing this along.
Volker
Begin forwarded message:
From: Till Kamppeter
Subject: Google Summer of Code 2025 - Mentors for OpenPrinting URGENTLY
needed!!!
Date: 10 April 2025 at 00:31:04 CEST
To: Aveek Basu
Hi,
we got 40 proposals of people interested to be a GSoC contributor for
OpenPrin
Hi all,
The list of discussion topics for the upcoming Qt Contributors Summit is
filling up nicely at https://wiki.qt.io/Qt_Contributor_Summit_2025_-_Program -
thanks for that!
One bit of feedback from the last Qt CS in Würzburg was that many would have
liked to see more roadmap and direction
Hi all,
we have had a few rounds in which we reviewed code in various Qt modules and
added security tags as per https://contribute.qt-project.org/quips/23
As expected, we learned a few things in the process, and are preparing a few
improvements and clarifications. One of the proposals is that
> On 14 Mar 2025, at 17:49, Marc Mutz via Development
> wrote:
>
> Hi,
>
> TL;DR: do _not_ approve patches that do not "pick-to:" according to
> QUIP-16 or explain in the commit message why they deviate.
>
> Long version:
>
> Just a reminder that QUIP-16¹ gives detailed instructions how far
> On 14 Mar 2025, at 08:22, Schmertmann, Lars via Development
> wrote:
>
> Hello together,
>
> sadly we need to support Windows Server 2016 for a while in our
> application (https://github.com/Governikus/AusweisApp) because the
> extended support of Microsoft is given until Jan 12, 2027.
> http
> On 7 Mar 2025, at 12:27, Ulf Hermann via Development
> wrote:
>
> On 3/7/25 10:48, Schimkowitsch Robert wrote:
>> We widely use BINDABLE in Q_PROPERTY (>500 places) because it removes a lot
>> of boilerplate from our C++ classes.
> > [...]
>> I have never had any issues using BINDABLE. I hav
> On 27 Feb 2025, at 09:37, Marc Mutz via Development
> wrote:
>
> Hi,
>
> TL;DR:
> - reminder that quadratic algorithms are rare, but easily introduced by
> sloppiness
> - request to change QUIP-16 to allow fixing quadratic behaviour in all
> branches
>
> Quadratic Bahaviour
>
> O(N²) beha
> On 12 Feb 2025, at 22:22, Sérgio Martins wrote:
>
> On Wed, Feb 12, 2025 at 10:44 AM Cristian Le via Development
> wrote:
>>
>> I want to gather some feedback about adding a .gitreview file for all repos.
>> The file would look like
>>
>> ```
>> [gerrit]
>> host=codereview.qt-project.org
>> pr
> On 31 Jan 2025, at 09:32, Giuseppe D'Angelo via Development
> wrote:
>
> On 30/01/2025 18:45, Thiago Macieira wrote:
>> On Thursday 30 January 2025 09:09:47 Pacific Standard Time Giuseppe D'Angelo
>> via Development wrote:
>>> Some of you may have noticed the lack of reports by Coverity Scan i
> On 28 Jan 2025, at 17:28, David Redondo wrote:
>
> Am Dienstag, 28. Januar 2025, 12:27 schrieb Pedro Bessa via Development:
>> Hi everyone,
>>
>> We already have a place and a time!
>>
>> Qt Contributor Summit 2025
>> 7-8 May, 2025
>> Munich, Germany
>>
>> More information coming soon.
>>
> On 20 Jan 2025, at 07:32, Jani Heikkinen via Development
> wrote:
>
> Hi!
> We have branched ’6.8.2’ from ‘6.8’ now. So from now on all changes targeted
> to Qt 6.8.2 release must have ‘Pick-to: 6.8.2’ and ‘6.8’ is for Qt 6.8.3.
> Please remember: do not try to add anything nice-to-haves
> On 16 Jan 2025, at 11:58, Marc Mutz via Development
> wrote:
>
> Hi,
>
> Groundhog Day...
>
> Like every API review, so also in 6.9, we have the discussions between
> proponents of scoped vs. unscoped enums in class scope.
Hi Marc,
Taking this a step back:
I recall that you agreed at t
We decided in Würzburg that deprecation doesn’t imply removal in the next major
version, and that a new macro (as added by Ivan) gives us the ability to make
our intentions explicit at time of deprecation.
We might learn things between time of deprecation and the next major release
that change
> On 19 Dec 2024, at 21:31, Jörg Bornemann via Development
> wrote:
>
> On 12/19/24 12:06 PM, Marc Mutz via Development wrote:
>
>> 1/
>> I today refused to perform a re-licensing of a .cpp file being renamed
>> to .qdoc.¹ QUIP-18² has no provisions for files transitioning between
>> what QUI
> On 19 Dec 2024, at 17:09, Volker Hilsheimer via Development
> wrote:
>
> I’ll do that tomorrow :)
>
> Volker
>
>
>> On 19 Dec 2024, at 16:59, Oliver Eftevaag wrote:
>>
>> Yes, I've had approver rights for about 3 years now 🙂
>>
rs) to include Qt
> Quick Dialogs?
>
> OliverFrom: Development on behalf of
> Volker Hilsheimer via Development
> Sent: Thursday, December 19, 2024 12:25 PM
> To: Alex Blasche
> Cc: development@qt-project.org
> Subject: Re: [Development] Nominating Oliver Eftevaag as m
I’m quite sure Oliver already had approver privileges, and the nomination was
for him to become maintainer of Qt Quick Dialogs (as a separately maintained
module, splitting it out from Qt Quick Controls which remains Mitch’s), which
I’ll take care off tomorrow :)
Volker
> On 19 Dec 2024, at 0
> On 13 Dec 2024, at 17:43, Glen Mabey wrote:
>
> Hello!
> Would anyone be willing to forecast when QtCharts or QtGraphs will be
> supported for the WASM platform?
> Also, a big help would be an indication of which one will arrive first.
> Best Regards,
> Glen
Hi Glen,
What do you see not wor
Approved in release team meeting just now. Please cherry-pick the change
manually, with other required changes that didn’t land in 6.9 yet (seems that
change alone results in a merge conflict in 6.9).
Volker
> On 9 Dec 2024, at 10:47, Tor Arne Vestbø wrote:
>
> The following change, that add
Hi,
I’ve pushed https://codereview.qt-project.org/c/qt/qtdoc/+/608704 with a few
things added to the whatsnew69.qdoc file that I cooked up for this release.
As with the last releases, use gerrit’s on-web editing function to amend this
change, which avoids constant conflicts when separate change
gnificant negative impact. E.g. in QDialogButtonBox, both orientation and
standardButtons are properties.
If there’s anything missing then that should be easy to fix.
Volker
> On 28.11.24 15:45, Volker Hilsheimer via Development wrote:
>>> On 28 Nov 2024, at 15:01, André Somers via D
> On 28 Nov 2024, at 15:01, André Somers via Development
> wrote:
>
> Hi Marcus,
>
> On 28-11-2024 14:29, Marcus Tillmanns via Development wrote:
>> Hi Shawn,
>>
>>> On 28. Nov 2024, at 13:15, Shawn Rutledge via Development
>>> wrote:
>>>
>>>
On Nov 28, 2024, at 09:08, Fabian Kosmale
> On 27 Nov 2024, at 02:18, Thiago Macieira wrote:
>
> On Tuesday 26 November 2024 16:32:20 Pacific Standard Time Tor Arne Vestbø
> via
> Development wrote:
>>> Someone who cares about Windows/MSVC may want to take the mantle here,
>>> because cpp-winrt will be disabled for C++17.
>>
>> Plea
> On 14 Nov 2024, at 17:00, Thiago Macieira wrote:
>
> On Thursday 14 November 2024 02:20:16 Mountain Standard Time Volker
> Hilsheimer
> via Development wrote:
>> Did you build Qt SCXML? Build fails now with:
>>
>> error: "qtmochelpers.h not found or t
> On 12 Nov 2024, at 03:48, Thiago Macieira wrote:
>
> The changes to moc are getting integrated. The next batch will include a
> change to the output revision number, so qtmetamacros.h and moc must match.
> Because we decided that moc does not need to keep compatibility, you may need
> to r
> On 23 Oct 2024, at 09:31, Lars Knoll via Development
> wrote:
>
> Hi everybody,
>
> Over the last year, I found that I do not have the time that is required as a
> maintainer of Qt Multimedia.
>
> Artem Dyomin has been taking over more and more of that work from me over the
> last two year
> On 4 Nov 2024, at 12:39, Volker Hilsheimer via Development
> wrote:
>> On 19 Aug 2024, at 14:12, Dimitrios Apostolou via Development
>> wrote:
>>
>> Reminder that this QUIP is still open for feedback:
>>
>> https://codereview.qt-project.org/c/met
> On 19 Aug 2024, at 14:12, Dimitrios Apostolou via Development
> wrote:
>
> Reminder that this QUIP is still open for feedback:
>
> https://codereview.qt-project.org/c/meta/quips/+/575276
>
> Concerns have been addressed and further feedback is welcome here or on
> codereview.
>
> Regards
> On 31 Oct 2024, at 14:51, Igor Khanin wrote:
>
> Greetings,
>
> I hope this is the right place to post this. I'm looking for advice as well
> as any historical context I can get.
>
> The documentation states that the `QTextFormat::LayoutDirection` text format
> property is both a paragrap
> On 28 Oct 2024, at 06:57, Thiago Macieira wrote:
>
> On Friday 18 October 2024 08:36:22 Pacific Daylight Time Thiago Macieira
> wrote:
>> I'm going to assume that silence is consent to "there is no drawback" and
>> will proceed with the implementation.
>
> It's been a week since I posted th
> On 24 Oct 2024, at 12:29, Ivan Solovev wrote:
>
> Hi Volker,
>
>> From my understanding, the idea behind the std::format framework would be
>> to have a “cardinality" type for which we can implement a special formatter,
>> allowing “whatever” to be in the format specification.
>
> True, but t
> On 23 Oct 2024, at 22:55, Thiago Macieira wrote:
>>> a) keep the "n" and make it mandatory, as in {n}
>>
>> If we use std::format, then we cannot do it, because it does the
>> argument index parsing on its own, and delegates to a custom formatter
>> specialization after that. And argument index
> On 21 Oct 2024, at 17:57, Phil Thompson via Development
> wrote:
>
> On 21/10/2024 16:49, Thiago Macieira wrote:
>> On Monday 21 October 2024 03:02:47 Pacific Daylight Time Phil Thompson via
>> Development wrote:
>>> In the QMetaProperty ctor it tries to resolve the QMetaEnum for the
>>> prope
> On 8 Oct 2024, at 01:41, Ilya Fedin wrote:
>
> On Mon, 07 Oct 2024 07:42:11 -0700
> Thiago Macieira wrote:
>
>> You're generalising. The fact that those contributions weren't wanted
>> or were misunderstood is not an indication that everyone's
>> contributions will suffer the same consequen
> On 3 Oct 2024, at 17:07, Phil Thompson via Development
> wrote:
>
> On 03/10/2024 15:44, Thiago Macieira wrote:
>> On Thursday 3 October 2024 05:06:08 GMT-7 Phil Thompson via Development
>> wrote:
>>> Yes, that's the change - commenting out the new test fixes the problem.
>>> I am dynamica
> On 24 Sep 2024, at 23:23, Mårten Nordheim via Development
> wrote:
>
> Hello,
>
> For a while now there has been "Quality of Service" APIs available for
> threads and processes in at least Apple[0] and Windows[1].
> Typically you can request either "Eco", and Default (i.e. the OS does its
> On 25 Sep 2024, at 13:09, Dimitrios Apostolou via Development
> wrote:
>
> On Wed, 25 Sep 2024, Assam Boudjelthia via Development wrote:
>
>> This would be very nice!
>> Also, consider removing the "Label Time Summary:” section from the logs
>> which outputs the run tests with their executio
> On 24 Sep 2024, at 15:12, Paul Wicking via Development
> wrote:
>
> Proposal:
>
> 1. Retain Existing `\since` Annotations: I propose that we keep the `\since
> [version]` annotations in the documentation, even for older versions like Qt
> 4.x, to preserve this valuable information for tho
> On 19 Sep 2024, at 16:18, Thiago Macieira wrote:
>
> On Thursday 19 September 2024 00:55:15 GMT-7 David Redondo wrote:
>> So related blog I read some time ago about this and the "natural order" of
>> qualifiers:
>>
>> https://quuxplusone.github.io/blog/2021/04/03/static-constexpr-whittling-kni
> On 27 Aug 2024, at 21:21, Thiago Macieira wrote:
>
> On Tuesday 27 August 2024 10:29:05 GMT-7 Ville Voutilainen wrote:
>> On Tue, 27 Aug 2024 at 17:15, Thiago Macieira
> wrote:
>>> The point is that this putative mistake has no consequences, today. It
>>> remains to be seen whether it will wit
> On 9 Aug 2024, at 17:52, Thiago Macieira wrote:
>
> On Friday 9 August 2024 01:46:02 GMT-7 Fabian Kosmale via Development wrote:
>> 1. Don't do anything; that's the behavior we have since at least Qt 5.
>> If the dtor doesn't actually throw, everything is fine; if it does
>> throw, we're callin
> On 15 Aug 2024, at 12:00, Jarno Lämsä via Development
> wrote:
>
> Hi,
>
> I would like to request a feature freeze exception for VxWorks input handling.
>
> https://codereview.qt-project.org/c/qt/qtbase/+/581635 Enable mouse handling
> on VxWorks
> https://codereview.qt-project.org/c/qt/qt
> On 4 Jun 2024, at 09:29, Jani Heikkinen via Development
> wrote:
>
> Hi!
> Qt 6.8 API Change Review is started, see
> https://bugreports.qt.io/browse/QTBUG-125859
> generated diffs are here:
> • https://codereview.qt-project.org/q/topic:api-change-review-6.8
> • https://codereview.qt
> On 11 Jul 2024, at 15:51, Giuseppe D'Angelo wrote:
>
> On 11/07/2024 15:21, Volker Hilsheimer wrote:
>> For many APIs, application code provides the data (perhaps indirectly),
>> e.g. to QDateTime::fromString. In that case we can assume that the
>> applica
> On 11 Jul 2024, at 13:26, Giuseppe D'Angelo via Development
> wrote:
>
> On 10/07/2024 19:08, Kai Köhne via Development wrote:
>> That's a lot of questions. But a lot comes down to: Can we agree on parts of
>> Qt that are more critical and, therefore, should be subject to additional
>> secur
Hi all,
The support for Common Print Dialog Backends has been in the works for a while.
As of last year we are provisioning the SDK in our CI nodes:
https://codereview.qt-project.org/c/qt/qt5/+/471258
but the change on Qt is stuck a bit. Could someone with experience and
knowledge about the st
> On 11 Jun 2024, at 21:08, Giuseppe D'Angelo via Development
> wrote:
>
> Il 11/06/24 07:12, Thiago Macieira ha scritto:
>> I'm arguing that such code is likely already broken (producing mojibake) for
>> non-US-ASCII content, so having U+FFFD instead of mojibake is not worse. You
>> wouldn't be
s in 6.7.x release will be
> reviewed as well
>
> br,
> Jani
>
>> -Original Message-
>> From: Volker Hilsheimer
>> Sent: perjantai 7. kesäkuuta 2024 17.13
>> To: Jani Heikkinen
>> Cc: development@qt-project.org
>> Subject: Re: [Developmen
>
> On 4 Jun 2024, at 09:29, Jani Heikkinen via Development
> wrote:
>
> Hi!
> Qt 6.8 API Change Review is started, see
> https://bugreports.qt.io/browse/QTBUG-125859
> generated diffs are here:
> • https://codereview.qt-project.org/q/topic:api-change-review-6.8
> • https://codereview
> On 3 Jun 2024, at 20:42, Björn Schäpers wrote:
>
> Am 03.06.2024 um 10:20 schrieb Volker Hilsheimer via Development:
>>
>>> On 3 Jun 2024, at 09:08, Phil Thompson via Development
>>> wrote:
>>>
>>> In my code I call QAudio::convertVol
> On 3 Jun 2024, at 09:08, Phil Thompson via Development
> wrote:
>
> In my code I call QAudio::convertVolume() (yet to migrate to the QtAudio
> namespace). This compiles fine against Qt v6.7.0 and v6.7.1 (from the online
> installers). However...
>
> Compiled against v6.7.0 the compiler
Cheers,
Volker
On 30 May 2024, at 19:18, Volker Hilsheimer wrote:
First set of changes are in, I pushed a second change now with a few more bits
and bobs based on a \since 6.8 grep. Not complete, so please go ahead and
review and amend within the gerrit UI.
Generous linking to the respective
First set of changes are in, I pushed a second change now with a few more bits
and bobs based on a \since 6.8 grep. Not complete, so please go ahead and
review and amend within the gerrit UI.
Generous linking to the respective API documentation is both a kindness to the
reader, and might also h
> On 29 May 2024, at 05:30, Kevin Kofler via Development
> wrote:
>
> Giuseppe D'Angelo via Development wrote:
>> 2) We stop guaranteeing forward binary compatibility within the same
>> minor version.
>>
>> In other words, code compiled against Qt X.Y.Z may or may not work if at
>> runtime Qt X
On 22 May 2024, at 17:31, Thiago Macieira wrote:
On Wednesday 22 May 2024 06:38:28 GMT-3 Volker Hilsheimer via Development
wrote:
As long as Qt is built with exception support
We don't support toggling that on and off any more and haven't for a while.
QtCore and QtGui are com
> On 22 May 2024, at 16:30, Volker Hilsheimer via Development
> wrote:
>
>> On 22 May 2024, at 13:20, Turtle Creek Software
>> wrote:
>>
>> When we posted this problem to the Interest list, Thiago replied that Qt is
>> not designed to pass along
ht be a step forward for you.
Addressing point 2) systematically to the point where we could claim that Qt
returns to a predictable state when application code throws would be, as
pointed out by Henry, a massive, and in practice unverifiable, undertaking.
Cheers,
Volker
> Thanks, Dennis
&
Hi Dennis,
> On 7 May 2024, at 21:05, Turtle Creek Software wrote:
>
> TurtleSoft posted on the Interest list earlier about problems we had with
> exception handling, and Thiago suggested I post here.
>
> Since the early 90s, our C++ code has had about 10,000 sanity checks which
> give an err
I agree that it’s important to get Beta1 out before summer vacation starts, but
we win very little by verifying that we can release the beta of a Qt Multimedia
that’s quite different from the Qt Multimedia we actually want to release.
The FFmpeg provisioning changes are localised to Qt Multimedi
Hi all,
It’s still a few weeks to go until we have Qt 6.8 feature freeze, and a quick
grep for `\since 6.8` tells me that a bunch of goodness has already landed.
However, the whatsnew68.qdoc document is still a bit empty. I’ve now pushed a
change that adds missing section etc to
https://codere
t initialized. We have some similar approaches
to trigger Qt Widgets specific behaviors from Qt Gui classes
(QGuiApplicationPrivate::closeAllPopups, for instance, or even
createActionPrivate/createShortcutPrivate).
Volker
ke 8. toukok. 2024 klo 12.51 Volker Hilsheimer via Development
(development
On 8 May 2024, at 07:32, Marc Mutz via Development
wrote:
On 07.05.24 18:46, Volker Hilsheimer wrote:
In the long run, a mechanism in Qt Core makes sense, IMHO. That “it’s a
browser” is not true for every possible call of the QDesktopServices API.
We need something _now_ for QtNetworkAuth
I’ve now updated the list of maintainers [1] with this change.
[1] https://wiki.qt.io/Maintainers
Thanks again Frank for your contributions to Qt OPC UA, for thank Jannis for
taking over!
Cheers,
Volker
> On 23 Apr 2024, at 13:16, Frank Meerkötter
> wrote:
>
> Hi qt-devel,
>
> I am going
> On 7 May 2024, at 17:51, Marc Mutz via Development
> wrote:
>>
>> It doesn't change the technical roadblock: you *cannot* *move*
>> QDesktopServices. The best you can do for API is add a new one.
>
> I'm pretty sure REMOVED_SINCE + an inline namespace around the Core
> version would enable a
> On 23 Apr 2024, at 14:06, Marc Mutz via Development
> wrote:
>
> Hi Frank,
>
> On 23.04.24 13:16, Frank Meerkötter wrote:
>> I am going to step down as the maintainer of Qt OPC UA. I have not been
>> very active recently.
>
> Thanks for your work on QtOpcUa over the years!
>
>> I would like to
On 15 Apr 2024, at 12:36, Tor Arne Vestbø via Development
wrote:
On 15 Apr 2024, at 12:07, Daniel Smith via Development
wrote:
I'd like to open up a thread for discussion on the addition of a new commit
message footer, "Reopens", related to Fixes/Task-Number.
The proposed behaviour is:
> On 13 Mar 2024, at 09:15, Eskil Abrahamsen Blomfeldt via Development
> wrote:
>
> Hi,
>
> I would like to nominate Hatem ElKharashy for maintainership of the Qt Svg
> module. This module currently does not have any active maintainer, but it has
> been part of my team's responsibility and ba
sführer: Mika Pälsi,
> Juha Varelius, Jouni Lintunen
> Sitz der Gesellschaft: Berlin,
> Registergericht: Amtsgericht
> Charlottenburg, HRB 144331 B
>
> From: Development on behalf of Dennis
> Oberst via Development
> Sent: Tuesday, March 19, 2024 12:12 PM
> To: Jean-Michaël Celeri
> On 18 Mar 2024, at 12:27, Dennis Oberst via Development
> wrote:
>
> Hello all,
>
> I'd like to request a new playground repository to continue the development
> of the "Clap Interface," a client-side library that uses QtGrpc to provide
> integration with the CLAP audio plugin standard, ult
breakage.
It doesn’t help with types like QObjectData and QArrayData, which are not
documented as \internal.
> On 07.03.24 10:09, Volker Hilsheimer wrote:
>>> On 4 Mar 2024, at 10:57, Marc Mutz via Development
>>> wrote:
>>>
>>> Hi,
>>>
On 18 Mar 2024, at 14:00, Giuseppe D'Angelo via Development
wrote:
On 18/03/2024 13:34, André Somers wrote:
While I know it's easy to work around, I sometimes find myself doing it
anyway. To me, it signals what API is intended to be used in what way.
That a class overrides `event` (or any other
> On 15 Mar 2024, at 12:30, Marc Mutz via Development
> wrote:
> On 15.03.24 09:11, apoenitz wrote:
>> On Fri, Mar 15, 2024 at 07:16:59AM +, Marc Mutz via Development wrote:
> [...]
>>> Please note that this means that any override (and all new QObject
>>> classes should contain one, since, i
> On 4 Mar 2024, at 10:57, Marc Mutz via Development
> wrote:
>
> Hi,
>
> TL;DR:
> - Treat all APIs not clearly marked as private (private access, *Private
> namespace or "We mean it!" comment) as public, in particular keep SC/BC
> and deprecate before remove.
> - Avoid adding APIs that are
On 6 Mar 2024, at 23:09, Axel Spoerl via Development
wrote:
Dear Colleagues,
I hereby nominate Dr. Máté Barany as an approver for the Qt project.
Máté has been a valuable contributor and reviewer, providing sound code,
guidance and input.
As a reference, see his dashboard
here:https://coderev
e
I'm not suggesting to do such a port for all plugins. XCB is just a test
balloon, but we might want to apply the #pragma once trick for new code
going forward.
Thanks,
Marc
On 12.10.22 12:35, Volker Hilsheimer via Development wrote:
>
>> On 11 Oct 2022, at 22:11, Thiago Macieira
On 4 Mar 2024, at 14:42, Kai Köhne via Development
wrote:
Hi,
I suggest extending our qt_attribution.json format to explicitly mark
third-party components not part of the Qt sources, like
https://doc.qt.io/qt-6/qtmultimedia-attribution-ffmpeg.html.
QUIP-7 change:
https://codereview.qt-pr
1 - 100 of 472 matches
Mail list logo
