Re: [Development] Failed to run configure.bat in qt/qt5 repository on Windows?

If the goal here is to build documentation, I recommend installing Qt from the installer, and then doing a local build with e.g.: cd ~/build/qt/6.x-doc && ~/dev/qt/configure -developer-build -nomake examples -nomake tests -no-warnings-are-errors -submodules qtbase,qtdoc -qt-host-path

Re: [Development] Nominating Axel Spoerl as approver

+1 Very impressed with his fearless adventures into the abyss of flakey tests! Cheers, Tor Arne > On 5 Dec 2022, at 10:57, Volker Hilsheimer via Development > wrote: > > Hi, > > > I’d like to nominate Axel Spoerl as an approver for the Qt project. > > Axel has been working in The Qt

Re: [Development] Nominating Mikołaj Boć as approver

+1! (I’m Mikołaj’s direct manager) On 21 Dec 2022, at 15:21, Morten Sørvig via Development wrote: Hi, I’d like to nominate Mikołaj Boć as an approver for the Qt project. Mikołaj joined the Qt Company earlier this year and hit the ground running. He has contributed features and many bug

Re: [Development] Nominating Mårten Nordheim and Timur Pocheptsov as new co-maintainers of Qt WebSocket

+1 > On 29 Nov 2022, at 14:55, Volker Hilsheimer via Development > wrote: > > Hi, > > > Kurt Pattyn is currently listed as the Maintainer fo Qt WebSocket. However, > he has not responded to emails I sent him over the last few months. In the > middle of October I informed him that I will

Re: [Development] New Qt example development guideline and revamping examples

> On 18 Jan 2023, at 13:12, Giuseppe D'Angelo via Development > wrote: > >> RECOMMENDED >>Prefer signal/slot connection with lambdas: >> https://doc.qt.io/qt-6/signalsandslots.html > > All the contrary, do NOT do that, as it results in 200+ lines unnamed > lambdas. Strongly prefer

Re: [Development] New Qt example development guideline and revamping examples

On 20 Jan 2023, at 09:49, Eike Ziller wrote: Am 19/01/2023 um 13:33 schrieb Giuseppe D'Angelo via Development : Il 19/01/23 10:27, Tor Arne Vestbø ha scritto: All the contrary, do NOT do that, as it results in 200+ lines unnamed lambdas. Strongly prefer named slots. Keep the lambdas short

Re: [Development] I ❤️ Qt containers! :) (was: How qAsConst and qExchange lead to qNN)

> On 8 Nov 2022, at 14:25, Volker Hilsheimer via Development > wrote:  Tor Arne ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

Re: [Development] Qt Multimedia: proposing behavior change to QAudioSink::resume

Hi, This does indeed look like an oversight, where the behavior was perhaps modeled under the assumption the buffers were empty at the time of suspend(). I would expect the state to return back to the same state the sink had when calling suspend(). Cheers, Tor Arne > On 30 Jan 2023, at

[Development] Archiving of the '6.x' version in JIRA

Hey all, We’re planning on archiving the '6.x’ version in JIRA: https://bugreports.qt.io/projects/QTBUG/versions/18732 Now that Qt 6 has been out for a while, the version

Re: [Development] Nominating Edward Welbourne as QLocale / date/time maintainer

+1! > 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 > already; making it de-jure sounds only logical. > > I asked, and he'd be

Re: [Development] API style guide: scoped enum or not?

> On 14 Jun 2023, at 17:48, Thiago Macieira wrote: > > On Wednesday, 14 June 2023 08:35:16 PDT Marc Mutz via Development wrote: > B) new enums MUST be scoped, also when nested in classes¹² -1 Disagree >>> >>> -1 Disagree >> >> Ok. But _why_? (Q to both) > > I'm inclined to

Re: [Development] API style guide: scoped enum or not?

On 14 Jun 2023, at 16:20, Allan Sandfeld Jensen wrote: On Mittwoch, 14. Juni 2023 14:59:40 CEST Marc Mutz via Development wrote: On 02.05.23 10:58, Volker Hilsheimer via Development wrote: During the header review, but also in API discussions leading up to it, we had a few cases where it would

Re: [Development] Nominating Artem Dyomin as Approver

+1! (Disclaimer: Artem reports to me directly). On 27 May 2023, at 18:02, Volker Hilsheimer via Development wrote: +1, he’s doing great. Disclaimer: Artem sits across the hall from me in the office, works down the street from me in home office, and reports to me indirectly. Volker

[Development] Bumping the minimum CMake version for Apple platforms to 3.21 for Qt 6.6

Hi all, We currently require CMake 3.16 for shared builds, and 3.21 for static builds. CMake 3.16 unfortunately doesn't have a feature we rely on on Apple platforms — finalizers — requiring us to maintain and take into account additional APIs for users to manually finalize their projects, with

Re: [Development] Changes to automatic cherry-picking

Thanks Daniel! This sounds like a better model with less chance of orphaned changes. > On 24 Jul 2023, at 10:07, Daniel Smith via Development > wrote: > […] > Because this change takes away some level of control from the user, a new > footer is being introduced. A new footer, proposed as

Re: [Development] API style guide: scoped enum or not?

On 3 May 2023, at 18:40, Giuseppe D'Angelo via Development wrote: Il 02/05/23 10:58, Volker Hilsheimer via Development ha scritto: During the header review, but also in API discussions leading up to it, we had a few cases where it would have helped if we had clearer guidelines about when to

Re: [Development] API style guide: scoped enum or not?

On 3 May 2023, at 19:22, Thiago Macieira wrote: I'd say that any new enumeration in the Qt namespace should be enum class, but enums in classes may not be so if they're sufficiently descriptive already. Agreed, and this is also what our current API design guide says:

Re: [Development] Nominating Piotr Wierciński for approval status

+1 :) > On 8 Feb 2024, at 09:39, Morten Sørvig via Development > wrote: > > I would like to nominate Piotr Wierciński for approver rights in the Qt > project. > > Piotr joined the Qt company early 2013 and has since then contributed to Qt > for WebAssembly. This includes many bugfixes and

Re: [Development] QML Rectangle corner radius API for Qt 6.7

On 22 Dec 2023, at 13:59, Lars Knoll wrote: You don't often get email from l...@knoll.priv.no<mailto:l...@knoll.priv.no>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> On 22 Dec 2023, at 13:54, Tor Arne Vestbø via Development wrote: On 22 Dec 20

Re: [Development] QML Rectangle corner radius API for Qt 6.7

> 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 grouped property containing the `topLeft`, >> `topRight`, `bottomLeft` and

Re: [Development] QML Rectangle corner radius API for Qt 6.7

On 22 Dec 2023, at 13:54, Tor Arne Vestbø wrote: We can change the `radius` property from a qreal into a group property with left/rigth/top/bottom, similar to anchors. We can detect in the setRadius setter if the incoming argument is a real, and apply that to all of the corners. That would

Re: [Development] QML Rectangle corner radius API for Qt 6.7

On 22 Dec 2023, at 13:59, André Somers wrote: And what type would the radius property return then? I guess it would have to be the grouped type. But that would break all code that currently creates a binding on radius expecting it to be a real. True, that would not work too well. The

Re: [Development] Stepping down as Android maintainer

Thanks for all your work BogDan! And a strong +1 to Assam! Tor Arne 8. jan. 2024 kl. 09:47 skrev BogDan Vatra via Development : Hello there, I have been less active on the Android port recently and Assam has been doing the majority of the work maintaining the Android port. I'm therefor

Re: [Development] Requesting a repository for Qt Interface Framework Reference APIs

If it’s an option to rename this module we should take the opportunity to do so I think. The problem of the generic naming came up in the past, but the understanding was that it was too late to change. If that is not the case after all, we should strongly consider it. The documentation at

Re: [Development] Requesting a repository for Qt Interface Framework Reference APIs

leftovers. There are developers/customers using it in their production environment already, also outside of the automotive sector. BR, Maurice From: Development On Behalf Of Tor Arne Vestbø via Development Sent: Thursday, 7 December 2023 18:37 To: Tuukka Turunen Cc: Macieira, Thiago ; development@qt-project.o

Re: [Development] Nominating Vlad Zahorodnii for approval status

+1! > On 1 Feb 2024, at 15:11, David Edmundson wrote: > > I would like to nominate Vlad Zahorodnii for approver rights in the Qt > project. > > Vlad has also been working on the QtWayland backend, providing insight > based on his other role as one of the kwin maintainers. > Vlad and I have

Re: [Development] Nominating David Redondo for approval status

+1! > On 1 Feb 2024, at 15:10, David Edmundson wrote: > > I would like to nominate David Redondo for approver rights in the Qt project. > > David's first contributions to Qt started in November 2020, but has > ramped up this last year working on the Qt Wayland platform. Not only > has he fixed

Re: [Development] Nominating Matthias Rauter for approval status

+1! On 30 Jan 2024, at 13:11, Paul Tvete via Development wrote: Hi, I would like to nominate Matthias Rauter as an approver for the Qt Project. Matthias has been working on Qt for more than a year now. In this time, he has done great work on Qt Location and Qt SVG, among other. I have had

Re: [Development] C++20 comparisons @ Qt (was: Re: C++20 @ Qt)

The naming makes sense, given their purpose. But can we put them in a dedicated Qt::std_compat namespace? Or is that too late? That would make it clear these are not Qt proper types (living in the Qt namespace), but dedicated compat types/BC/SC vehicles . Tor Arne On 14 Nov 2023, at 10:00,

Re: [Development] RFC: New keyword for Fixes bot "Reopens" and revert detection

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: * Use of "Reopens: QTBUG1234" would trigger automatic reopening of

Re: [Development] Moving QDesktopServices from Gui to Core?

There’s some overlap here with the more modern features of intents, activities, etc, which we are hoping to add proper APIs for at some point, so I suggest not doing any public API changes as part of this. We can move the registration APIs to QtCore as private APIs, that QtNetworkAuth can use,

Re: [Development] Moving QDesktopServices from Gui to Core?

> On 6 May 2024, at 13:06, Juha Vuolle wrote: > >> QtNetworkauth leaves the QDesktopServices::openUrl() usage/non-usage >> at the user's discretion, and thus that currently won't force a Gui >> dependency. > > (Ah shoot. Correcting myself, in the new qtnetworkauth class we do > need to call

Re: [Development] Moving QDesktopServices from Gui to Core?

> On 6 May 2024, at 12:31, Allan Sandfeld Jensen wrote: > > On Monday 6 May 2024 10:02:43 CEST Tor Arne Vestbø via Development wrote: >> There’s some overlap here with the more modern features of intents, >> activities, etc, which we are hoping to add proper APIs for a

Re: [Development] Moving QDesktopServices from Gui to Core?

> On 8 May 2024, at 07:32, Marc Mutz via Development > wrote: > > I'd like an option that actually solves for the needs of QtNetworkAuth. 1. Move the plumbing of the URL handling to private APIs in QtCore, used by QDesktopServices 2a. Add a helper

Re: [Development] Moving QDesktopServices from Gui to Core?

> On 7 May 2024, at 12:51, Marc Mutz via Development > wrote: > > On 06.05.24 13:08, Tor Arne Vestbø via Development wrote: >> >> >>> On 6 May 2024, at 13:06, Juha Vuolle wrote: >>> >>>> QtNetworkauth leaves the QDesktopServices::o

[Development] Nominating Jøger Hansegård for approver rights

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 lately focusing on color management. Jøger is a thorough and responsible engineer and I trust that

Re: [Development] Nominating Dr. Máté Barany as an approver for the Qt project

+1! 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

Re: [Development] Using '#pragma once' instead of include guards?

The choice of where we use/allow `#pragma once` should not be coupled to whether a header is considered public or not. Let’s not create even more indirections and inference rules that one has to keep in mind. If we want to make it clearer if a header is public or not, let’s make it explicit.

Re: [Development] Nominating Tim Blechmann for approver

+1!!! > On 22 May 2024, at 10:52, Jøger Hansegård via Development > wrote: > > Hi all, > > I would like to nominate Tim Blechmann for approver rights in the Qt project. > > Since 2013, Tim has been an active contributor to Qt, providing strong > patches and insightful reviews. Currently, he

Re: [Development] Qt for WebAssembly status update

Nice overview, thanks Morten! Tor Arne On 6 Jun 2024, at 13:20, Morten Sørvig via Development wrote: Hello all, It’s been a while since the previous update so I figured it was time for a small “state of the union” on the WebAssembly port. I’ll focus on topics which are most relevant to