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
me 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@qt-project.org) kirjoitt
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
> 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
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,
ible 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
> 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,
> 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
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
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 wrote:
>>
>> On Tuesday, 11 October 2022 12:25:13 PDT Kyle Edwa
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:
I haven’t heard any convincing argument for us raising the minimum to C++ 20 in
the foreseeable future. Not for building Qt, and not for using Qt.
At most we get some convenience constructs for ourselves. There’s value in
that, of course. But unless I miss something huge, then that value is
+1!
Volker
On 8 Feb 2024, at 09:48, Eskil Abrahamsen Blomfeldt via Development
wrote:
+1
Although I think 2013 should be 2023.
Eskil Abrahamsen Blomfeldt
Senior Manager, Graphics
The Qt Company
Sandakerveien 116
0484 Oslo, Norway
From what I see, the open questions from the thread in May are still:
- (paraphrasing Ville) which C++ 20 features are worth breaking (primarily
embedded) users who want new Qt version but don’t yet have the compilers that
can give them these facilities?
+1
Volker
> 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
> On 22 Jan 2024, at 22:15, Giuseppe D'Angelo via Development
> wrote:
>
> Il 22/01/24 19:03, Shawn Rutledge via Development ha scritto:
>> I guess your goal is to be able to see it in the header rather than having
>> to look up the docs in the cpp file or online? (Alternatively we could
>>
On 5 Dec 2023, at 13:13, Volker Hilsheimer via Development
wrote:
On 3 Dec 2023, at 12:08, apoenitz wrote:
On Sat, Dec 02, 2023 at 11:25:16AM +0100, Giuseppe D'Angelo via Development
wrote:
On 30/11/2023 19:39, apoenitz wrote:
I propose to make this setup an official Module of Qt Creator
> On 22 Dec 2023, at 13:59, Lars Knoll via Development
> wrote:
>
>>
>> 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
> On 17 Dec 2023, at 14:16, Marc Mutz via Development
> wrote:
>
> On 16.12.23 10:20, apoenitz wrote:
>> Recently there were two serious regression on the Qt side due to "just using
>> string views" (which would also be formally permitted), and I've seen now a
>> patch that changes a map to a
> On 15 Dec 2023, at 16:19, Sune Vuorela wrote:
>
> On 2023-12-15, Elias Steurer via Development
> wrote:
>> No, I still need all the get/set/notify functions to change/get the
>> variables from the outside. There is currently no way to do that, or am
>> I missing something? Something like
Hi,
For Qt 6.7 we have made a bunch of changes to the QJniObject class and the
so-far-undocumented macros from QtJniTypes. Also, the code structure has
changed quite a bit. This change is the diff of the qjni* headers from 6.6 to
6.7:
https://codereview.qt-project.org/c/qt/qtbase/+/524298
If
> On 8 Dec 2023, at 15:06, Jani Heikkinen via Development
> wrote:
>
> Hi!
> Qt 6.7 Feature Freeze will be in effect today. If your changes are ready and
> approved by the end of today, you can still continue staging those in 'dev'
> over the weekend. The plan is to branch from "6.7" to
timents that I can identify in that discussion, two can
be addressed to some degree by a buddy group that proactively reaches out to
lower the learning curve.
Volker
> On 12/5/2023 9:57 AM, Volker Hilsheimer via Development wrote:
>> At the Qt Contributors Summit in Berlin
The request at hand is to move two of the reference APIs that are based on the
interface framework out into a separate qt-labs repository. Those two APIs are,
as Dominik pointed out, very automotive specific. But just because they are
based on the interface framework doesn’t mean that we need
> On 3 Dec 2023, at 12:08, apoenitz wrote:
>
> On Sat, Dec 02, 2023 at 11:25:16AM +0100, Giuseppe D'Angelo via Development
> wrote:
>> On 30/11/2023 19:39, apoenitz wrote:
>>> I propose to make this setup an official Module of Qt Creator, and herewith
>>> also nominate Jarek as Maintainer.
At the Qt Contributors Summit in Berlin last week, we discussed various ideas
around improving the contribution experience, esp for new people.
One action that came out of that was setting up a gerrit group of people that
are able and willing to hand-hold new contributors through the process.
> On 6 Nov 2023, at 15:55, Alex Blasche via Development
> wrote:
>
> Hi,
>
> Qt GRPC and Qt Protobuf were added to Qt a while ago. However until now they
> have been in Tech Preview mode. As we investigate the remaining issues which
> might prevent us from leaving TP, we need to address the
On 14 Nov 2023, at 10:00, Volker Hilsheimer via Development
wrote:
On 14 Nov 2023, at 09:40, Marc Mutz via Development
wrote:
On 14.11.23 09:31, Marc Mutz via Development wrote:
[...]
And then naming them Qt::partial_ordering is just consequent, because
users can reach ultimate SC by doing
> On 14 Nov 2023, at 09:40, Marc Mutz via Development
> wrote:
>
> On 14.11.23 09:31, Marc Mutz via Development wrote:
> [...]
>> And then naming them Qt::partial_ordering is just consequent, because
>> users can reach ultimate SC by doing something like
>>
>> #ifdef
On 21 Oct 2023, at 10:02, Haowei Hsu wrote:
Hello, Qt Development Team.
Recently, I successfully built docs of Qt-6.6.0 in MSYS/MINGW64 shell with the
following commands:
1. cd /c/Test/qt-everywhere-src-6.6.0
2. mkdir build && cd build
3. mkdir mingw-release && cd mingw-release
> On 19 Oct 2023, at 15:55, Phil Thompson via Development
> wrote:
>
> On 19/10/2023 12:07, Giuseppe D'Angelo via Development wrote:
>> On 19/10/2023 12:07, Phil Thompson via Development wrote:
>>> Up until v6.6 upgrading to a new version was relatively low risk but this
>>> will just
> On 19 Oct 2023, at 13:07, Giuseppe D'Angelo via Development
> wrote:
>
> On 19/10/2023 12:07, Phil Thompson via Development wrote:
>> Up until v6.6 upgrading to a new version was relatively low risk but this
>> will just encourage people to stay on older versions. Is this a mistake or a
>>
On 13 Sep 2023, at 16:25, Volker Hilsheimer via Development
wrote:
On 13 Sep 2023, at 13:23, Ahmad Samir wrote:
On 13/9/23 11:06, Ivan Solovev via Development wrote:
I would therefore propose to remove the file from qt5.git:
+1 from my side.
I believe I simply do not have the clang-format
On 19 Sep 2023, at 15:49, Marc Mutz via Development
wrote:
So I ask: Please let us roll out the framework with one of
equal/eq/order/ordering/cmp (your choice, but quickly!), to set a status
quo against which to benchmark any potentially-superior solutions, and
then the ML can finish
> On 18 Sep 2023, at 14:46, Marc Mutz via Development
> wrote:
>
> TL;DR: "a" must not be a name of an existing function in Qt.
>
> On 18.09.23 10:15, Ivan Solovev via Development wrote:
>> Hi,
>>
>>> 1. an ADL-able calling convention: `using std::swap; swap(lhs, rhs);`
>>> 2. an
> On 16 Sep 2023, at 02:05, Henry Skoglund wrote:
>
> On 2023-09-16 01:55, Giuseppe D'Angelo via Development wrote:
>> Wrong mailing list?
>>
>> Il 16/09/23 01:41, Henry Skoglund ha scritto:
>>> S a;
>>> S b = a.clone();
>>>
>>> it seems to work like a charm (6.5.2 on Linux and the Mac.
On 13 Sep 2023, at 13:23, Ahmad Samir wrote:
On 13/9/23 11:06, Ivan Solovev via Development wrote:
I would therefore propose to remove the file from qt5.git:
+1 from my side.
I believe I simply do not have the clang-format tool installed on my system,
because it usually breaks the formatting of
Hello all,
I would like to nominate Ahmad Samir for approver rights in the Qt project.
For many months, Ahmad has produced a consistent flow of good contributions and
reviews to Qt:
Changes owned:
* https://codereview.qt-project.org/q/owner:a.samirh78%2540gmail.com
Changes commented/voted on:
During the recent maintenance window we have enabled the “mentions” feature of
gerrit:
https://www.gerritcodereview.com/3.7.html#mention-user-support
It’s not the pinnacle of usability in that you need to know the exact
username/email address of the user you want to mention (so you have to
> On 31 Aug 2023, at 19:15, Thiago Macieira wrote:
>
> On Thursday, 31 August 2023 09:54:37 PDT Lisandro Damián Nicanor Pérez Meyer
> wrote:
>>> It seems very unlikely that one would end up building for Qt x.y.z and
>>> then have their users on Qt x.y.(w>
>> With my Debian hat on: I really
y support the
> process/development.
>
> --
> Alex
>
>
>
> From: Development on behalf of team
> fluentmq
> Sent: Sunday, August 27, 2023 03:55
> To: Volker Hilsheimer; development@qt-project.org
> Subject: Re: [De
> On 26 Aug 2023, at 10:09, Ulf Hermann via Development
> wrote:
>
> Hi,
>
> The usual way to request a repository, playground or not, is a mail like this:
>
> https://lists.qt-project.org/pipermail/development/2022-August/042900.html
>
> If the request is not totally outlandish it's usually
> On 25 Aug 2023, at 14:20, Ahmad Samir wrote:
>
> On 25/8/23 14:11, Cristian Adam via Development wrote:
>> The other way of fixing this is by using ... macros. The article at c++ -
>> Importing inline functions in MinGW - Stack
>>
> On 24 Aug 2023, at 14:43, Lars Knoll via Development
> wrote:
>
>
>> 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
>>>
Thanks for the background info, Cristian!
It’s fine to agree that, for new code, the inline goes only on the declaration,
and must not be on the definition.
For existing code: throwing the somewhat but not totally (I think) naive regexp
Hello QtFluentMQ Team,
The project as you have described it sounds very cool and could be interesting
for many Qt users building distributed systems. So thanks for the work so far
and for reaching out!
As for providing a repository on our gerrit server for your project, and
perhaps moving it
On 23 Aug 2023, at 08:35, Haowei Hsu wrote:
Hello, Thiago.
No, I mean, why do you want to get Qt 6.2.4 in the first place?
I didn't say that it had to be 6.2.4. In fact, I've also tried to build other
Qt6 releases, such as: 6.1, 6.3, 6.5... etc.
However, I found during the process that when
> On 23 Aug 2023, at 15:09, Edward Welbourne via Development
> wrote:
>
> Lars Knoll (23 August 2023 13:32) wrote
>> We have been adding new enum values in certain cases. The operating
>> system versions needing to be amended to support a new version of
>> macOS is one example. That has
Hi,
Emails in which we nominate contributors for Approver status usually have two
queries: the list of changes owned [1], and the list of changes that the
nominee reviewed [2].
[1] https://codereview.qt-project.org/q/owner:volker.hilsheimer%2540qt.io
[2]
+1
Disclaimer: Kwanghyo reports (indirectly) to me.
Volker
On 14 Aug 2023, at 08:54, Tomi Korpipää via Development
wrote:
Hi,
I'd like to nominate Kwanghyo Park for approver status. He is the main
developer for Surface3D graphs for the QtGraphs module, and has been
contributing to
> On 20 Jul 2023, at 16:17, Fabian Kosmale via Development
> wrote:
>> Hi everyone,
>>
>> something that came up during this year’s KDE Akademy was that we
>> believe Q_PROPERTY should be able to handle std::optional, such that you
>> get a null QVariant out of it if it has no value. The main
> On 12 Jul 2023, at 09:52, EXT Mitch Curtis via Development
> wrote:
>
> Hi Arno,
>>
>> Hey everyone,
>>
>> what is the policy for adding behavior-changing bugfixes to patch-level
>> releases? Is this something to expect?
>> At the moment we operate under the assumption that bumping the
> Am 10.07.2023 um 18:02 schrieb Giuseppe D'Angelo via Development:
>> Hi,
>>
>> https://codereview.qt-project.org/c/qt/qtbase/+/487560 introduces
>> QT_NO_CONTEXTLESS_CONNECT , a macro that disables the 3-arguments connect --
>> in other words, it disables the
>>
>>>
On 26 Jun 2023, at 09:39, EXT Amir Abdol via Development
wrote:
Hi,
Unity Build is now enabled on CI for Qt Base, on dev branch, for the following
platforms: INTEGRITY, Windows 10 MinGW, Windows 11 MinGW, which are among the
slowest platforms on our CI.
Here is a brief note about the unity
On 20 Jun 2023, at 16:24, Arno Rehn wrote:
On 20.06.2023 16:12, Jani Heikkinen via Development wrote:
Qt 6.5 status:
- Branching from '6.5' to '6.5.2' done
- Qt 6.5.2 content is not frozen yet. The target is to freeze the Qt 6.5.2
content later this week
- The target is to release Qt 6.5.2
> On 14 Jun 2023, at 14:59, Marc Mutz via Development
> wrote:
[…]
> C) scoped enums SHOULD NOT repeat (part of) an enum's type name in the
> enumerators²
[…]
> I have been told today that QML allows scoped C++ enums to be used
> without the scope. If this is true, it should be fixed to
On 31 May 2023, at 16:05, Thiago Macieira wrote:
On Wednesday, 31 May 2023 00:17:21 PDT Marc Mutz via Development wrote:
I doubt there's an accepted project-wide standard, yet, but as a rule of
thumb that everyone might be able to agree on: If the function doesn't
store the string as-is (=parses
> On 16 Jun 2023, at 20:25, Thiago Macieira wrote:
>
> On Friday, 16 June 2023 11:05:30 PDT Giuseppe D'Angelo via Development wrote:
>> On 16/06/2023 18:00, Thiago Macieira wrote:
>>> On Friday, 16 June 2023 01:06:33 PDT Stephen Kelly wrote:
Make sure you're not hitting
+1 to A and C.
> On 14 Jun 2023, at 21:49, Allan Sandfeld Jensen wrote:
>
> On Mittwoch, 14. Juni 2023 17:48:27 CEST 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¹²
>
>
On 9 Jun 2023, at 02:00, Thiago Macieira wrote:
On Wednesday, 7 June 2023 19:18:02 PDT JiDe Zhang wrote:
please make sure your contribution uses QMetaCallEvent.
Why uses QMetaCallEvent? I don't know how to make the function arguments to
void** for QMetaCallEvent constructor. Maybe I can use
> On 7 Jun 2023, at 17:20, Thiago Macieira wrote:
>
> On Wednesday, 7 June 2023 01:53:47 PDT JiDe Zhang wrote:
>> I am writing a tool to allowed call a function in the specified existing
>> thread, I want to contribution it to Qt project, are you like?
>
> We do this internally, but don't
On 5 Jun 2023, at 09:11, Jukka Jokiniva via Development
wrote:
Hi,
There are quite many changes trying make it to the qt/qt5 dev branch:
https://codereview.qt-project.org/q/project:qt/qt5+branch:dev+is:open
If everyone starts to stage these individually, I am afraid that nothing will
get
> On 4 Jun 2023, at 23:26, Thiago Macieira wrote:
>
> On Sunday, 4 June 2023 11:51:54 PDT Marc Mutz via Development wrote:
>>> The other problem is I want to take a second, thorough look at your
>>> #ifdefs
>>> for C++20. I have a feeling some of the changing return types are a recipe
>>> for
> On 3 Jun 2023, at 16:54, Thiago Macieira wrote:
>
> On Saturday, 3 June 2023 02:54:49 PDT Marc Mutz via Development wrote:
>> The container-assign epic is partially merged. What's left is
>> QString::assign(), and there only the assign(it, it) part. If we release
>> as-is (with step 1, cf.
+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
From: Development on behalf of Lars Knoll
Sent: Saturday, May 27, 2023 5:41:42 PM
To: Qt
> 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 on
> On 12 May 2023, at 09:12, Tomi Korpipää via Development
> wrote:
>
> Hi,
>
> I'd like to nominate Jere Tuliniemi for approver status. He has been working
> with Qt for several years, contributing to Qt 3D Studio, ogl-runtime,
> QtQuick3D, Qt 3D, and QtGraphs to name a few. You can see his
I suppose it would have been useful to include date and time information as
well: Monday, May 22nd, 16:00 CEST.
Volker
> On 13 May 2023, at 14:08, Volker Hilsheimer via Development
> wrote:
>
> Hi,
>
>
> I’d be happy for comments and feedback to the C++ and QML APIs
Hi,
I’d be happy for comments and feedback to the C++ and QML APIs we added to the
Qt TextToSpeech module for Qt 6.6.
https://doc-snapshots.qt.io/qt6-dev/whatsnew66.html#qt-texttospeech-module
https://doc-snapshots.qt.io/qt6-dev/newclasses66.html (new member function in
the QTextToSpeech
> On 10 May 2023, at 07:39, Marc Mutz via Development
> wrote:
>>
>>
>> That said. I find discussing style-guides in general a waste of time, and
>> will
>> agree to anything that make us stop wasting time on this.
>
> I tend to agree, but the choice is either to define it centrally, or you
> On 2 May 2023, at 11:36, Edward Welbourne wrote:
>> This email is the anchor for various topics. I’ll start with a few
>> threads with things that I remember and feel could be improved. If you
>> have something new, please start a new thread in reply to this email, ...
>
> OK, then (see
> On 4 May 2023, at 17:34, Marc Mutz via Development
> wrote:
>
> On 04.05.23 15:38, Volker Hilsheimer via Development wrote:
>> Should we have Qt::TextLayout::Horizontal and Qt::Layout::Horizontal? Or
>> QSlider::Orientation::Horizontal?
>
> Without loo
On 3 May 2023, at 19:32, A. Pönitz wrote:
On Wed, May 03, 2023 at 03:21:40PM +0200, Giuseppe D'Angelo via Development
wrote:
Il 02/05/23 12:34, Volker Hilsheimer via Development ha scritto:
What started as an attempt to provide a few building blocks for making it
easier to build asynchronous
> On 3 May 2023, at 19:20, Thiago Macieira wrote:
> On Wednesday, 3 May 2023 08:56:07 PDT Volker Hilsheimer via Development wrote:
>> However, C++23 adds a bunch of improvements, and perhaps it’s a much smaller
>> challenge for compiler vendors to support after
> On 3 May 2023, at 18:40, Giuseppe D'Angelo via Development
> wrote:
>> But sometimes it’s also creating too much verbosity to use a scoped enum
>> (ie. Qt::Orientation::Horizontal would perhaps not be an improvement).
>
> I wouldn't consider this tiny bit of extra verbosity a huge
> 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 on
Bumping this thread up in your inboxes as it includes the links to the JIRA
tickets where the journey towards C++20 has been planned and discussed so far.
Let's try to build on what we already know.
The standing proposal is to move to C++20 with Qt 6.9, after the next LTS
release. I see no
On 3 May 2023, at 15:21, Giuseppe D'Angelo via Development
wrote:
Il 02/05/23 12:34, Volker Hilsheimer via Development ha scritto:
What started as an attempt to provide a few building blocks for making it
easier to build asynchronous APIs taking any kind of callable (like
QTimer::singleShot
Hi,
What started as an attempt to provide a few building blocks for making it
easier to build asynchronous APIs taking any kind of callable (like
QTimer::singleShot or QHostInfo::lookupHost) [1] has turned into a bit of a
longer journey to the core.
[1]
With Qt 6.5, it’s been a struggle to get people to respond and follow-up to
comments made during the header review process.
Gerrit doesn’t really care about @user-style mentioning in comments, even
though is seems that some people assume that it does. Creating JIRA tickets is
the official way
During header review we identified a few cases where e.g. using
std::conjunction/disjunction wasn’t used, or not used optimally. Using
suboptimal constructs can result in significant compile-time penalties.
We generally don’t have a lot of guidelines for template-meta-programming.
Should we
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 use scoped enums, and when not.
Scoped enums have some clear technical advantages (such as better type safety,
thanks to no implicit
Hi,
With Qt 6.5 out for a while already, and roughly a month to go until Qt 6.6
feature freeze and the start of the various activities that lead up to the
release, it’s perhaps not too early to review some of the pain points we
experienced with 6.5, and discuss how we can improve.
In
Hi,
Thanks, but please push patches to our code review system for discussing and
eventually merging changes:
* https://wiki.qt.io/Qt_Contribution_Guidelines
* https://wiki.qt.io/Setting_up_Gerrit
Regards,
Volker
> On 6 Apr 2023, at 14:16, shengfeng zhou wrote:
>
>
> On 22 Mar 2023, at 18:58, Christian Ehrlicher wrote:
>
> Am 22.03.2023 um 17:35 schrieb Volker Hilsheimer via Development:
>> But we use toLocal8Bit in plenty of cases as well. For instance in our Qt
>> SQL APIs.
>
> The only plugin which really uses toLocal8
> On 22 Mar 2023, at 12:07, Alvin Wong via Development
> wrote:
> On 22/3/2023 17:58, Lars Knoll wrote:
>> 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
Hi,
As part of the ongoing example revamping activity [1], we are also merging or
removing some examples. Qt 6.4 shipped with close to 650 examples. That’s a lot
of examples for users to navigate and grep through, and a lot of code for us to
maintain and keep relevant.
Some of those were
modules. What’s missing is the ‘process untrusted content’ flag, which is easy
to add:
https://codereview.qt-project.org/c/meta/quips/+/461983
Tell me what you think.
Regards
kai
From: Development
mailto:development-boun...@qt-project.org>>
On Behalf Of Volker Hilsheimer via Developmen
Hi,
the work has been happening in the wip/NG branch:
https://codereview.qt-project.org/gitweb?p=qt/qtdatavis3d.git;a=shortlog;h=refs/heads/wip/NG
Note that we want to (ultimately and over time) cover the functionality of Qt
Charts in this new implementation as well.
Volker
> On 13 Feb
To: Volker Hilsheimer , Jani Heikkinen
Cc: development@qt-project.org
Subject: Re: [Development] Proposal: let's change the release schedules a bit
Hi,
One of the main problems we face every time with the feature freeze is a lot of
changes coming in just before the deadline. While this is quite
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 16:38, Volker Hilsheimer via Development
wrote:
Hi,
TL;DR: I’d like to change
Hi,
A few days ago we had a lot of cherry-picks into 6.5 branches that hadn't
merged, for various reasons. Thanks to some copious stage-button-mashing during
the last days, that list is now rather short. Nevertheless, please have a look
at the unmerged cherry-picks anyway:
> On 23 Jan 2023, at 16:07, Kai Köhne wrote:
>
> Hi,
>
>> -Original Message-
>> From: Development On Behalf Of
>> [...]
>> This is a binary compatibility breakage of sorts. Applications that were
>> linked
>> against Qt 6.4 or Qt 6.5, and want to run against Qt 6.6 won’t work unless
Hi,
TL;DR: I’d like to change QAudioSink::resume() to always change the sink to
Active state, no matter how the sink was start()’ed.
QAudioSink provides low-level access to an audio device, allowing applications
to provide PCM data.
The class operates in one of two modes: in pull mode, the
1 - 100 of 389 matches
Mail list logo
