[Development] Amending QUIP 16 to document cherry-picking exceptions for refactorings

Hi, I would like to get input on this amendment to QUIP 16: https://codereview.qt-project.org/c/meta/quips/+/608523 It addresses exceptions to the cherry-picking policy for refactorings. Cheers. -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/develo

Re: [Development] HEADS-UP: Branching from 'dev' to '6.9' done & Qt 6.9 Feature Freeze is in effect

Hi, I'd like to request an exception for https://codereview.qt-project.org/c/qt/qtdeclarative/+/554020, which was approved before the freeze but hasn't successfully integrated yet. Thanks. > -Original Message- > From: Development On Behalf Of > Jani Heikkinen via Development > Sent: M

Re: [Development] Nominating Oliver Eftevaag as maintainer of Qt Quick Dialogs

+1 Disclaimer: I work in the same team. > -Original Message- > From: Development On Behalf Of > Shawn Rutledge via Development > Sent: Saturday, 30 November 2024 5:30 AM > To: Qt Development > Subject: [Development] Nominating Oliver Eftevaag as maintainer of Qt Quick > Dialogs > > I'm

Re: [Development] Flakey tests heatmap analysis

Hi, Once I've gotten into a specific filter (i.e. https://testresults.qt.io/grafana/d/de08wetl3yq68f/Test%20failure%20heatmaps?var-integration=149569&var-table_name=blacklisted_tests&var-project=qt%2Fqtdeclarative&var-config=macos-13-arm64-developer-build-tests), is there a way to see a list of

Re: [Development] Proposal to retain \since version information in Qt Documentation

hand, asking users to refer to archived versions of the docs is not unreasonable, especially for such old versions. I'd still argue that there's more benefit to the user having that added convenience, though. From: Development on behalf of EXT Mi

Re: [Development] Proposal to retain \since version information in Qt Documentation

I'm confused... \since does show up in the generated documentation: - https://doc.qt.io/qt-6/qml-qtquick-item.html#focusPolicy-prop - https://doc.qt.io/qt-6/qml-qtquick-listview.html#displayMarginBeginning-prop For what it's worth, my vote goes for keeping that information too. As a user it's mu

Re: [Development] QtGraphs final API review

> -Original Message- > From: Development On Behalf Of > Sami Varanka via Development > Sent: Tuesday, May 14, 2024 6:42 PM > To: development@qt-project.org > Subject: [Development] QtGraphs final API review > > Hi everybody! > QtGraphs will be out of TP in 6.8, and now we need to do the f

Re: [Development] Nominating Matthias Rauter for approval status

+1 > -Original Message- > From: Development On Behalf Of > Paul Tvete via Development > Sent: Tuesday, January 30, 2024 8:11 PM > To: Qt development mailing list > Subject: [Development] Nominating Matthias Rauter for approval status > > Hi, > > I would like to nominate Matthias Rauter

Re: [Development] QtQuick Dialogs Widgets fallback

> -Original Message- > From: Kai Uwe Broulik > Sent: Thursday, August 24, 2023 7:38 PM > To: EXT Mitch Curtis ; development@qt-project.org > Subject: Re: [Development] QtQuick Dialogs Widgets fallback > > Hi, > > Which style are you referring to here? >

Re: [Development] QtQuick Dialogs Widgets fallback

> -Original Message- > From: Development On Behalf Of > Kai Uwe Broulik > Sent: Wednesday, August 23, 2023 4:17 AM > To: development@qt-project.org > Subject: [Development] QtQuick Dialogs Widgets fallback > > Hi everyone, Hi Kai, > we found that the Qt Quick Dialogs (MessageDialog and

Re: [Development] Behavior-changing bugfixes in patch-level releases

> -Original Message- > From: Arno Rehn > Sent: Wednesday, July 12, 2023 4:13 PM > To: EXT Mitch Curtis ; Qt development mailing list > > Subject: Re: [Development] Behavior-changing bugfixes in patch-level releases > > Hi Mitch, > > On 12.07.2023

Re: [Development] Behavior-changing bugfixes in patch-level releases

Hi Arno, > -Original Message- > From: Development On Behalf Of > Arno Rehn > Sent: Wednesday, July 12, 2023 3:01 PM > To: Qt development mailing list > Subject: [Development] Behavior-changing bugfixes in patch-level releases > > Hey everyone, > > what is the policy for adding behavior

Re: [Development] Nominating Santhosh Kumar Selvaraj for approver rights

+1 > -Original Message- > From: Development On Behalf Of > Jan-Arve Sæther via Development > Sent: Wednesday, June 21, 2023 2:56 AM > To: Jack Simcox via Development > Subject: [Development] Nominating Santhosh Kumar Selvaraj for approver > rights > > Hello all, > > I would like to nom

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

+1 > -Original Message- > From: Development On Behalf Of > Marc Mutz via Development > Sent: Thursday, May 4, 2023 6:10 PM > To: development@qt-project.org > Subject: [Development] Nominating Edward Welbourne as QLocale / > date/time maintainer > > Hi, > > I'd like to nominate Eddy as t

Re: [Development] Qt code browser url changed (cgit <-> cgit.cgi)?

The source code text seems to be missing - the line numbers seem to be correct by I don't see any code. Inspecting the HTML shows that there is no text there, so it's not just a CSS issue. > -Original Message- > From: Development On Behalf Of > Andrey Leman via Development > Sent: Monda

Re: [Development] Using QtCreator for Qt development

> -Original Message- > From: Development On Behalf Of > Eike Ziller via Development > Sent: Monday, 12 December 2022 5:20 PM > To: Владимир Белявский > Cc: development@qt-project.org > Subject: Re: [Development] Using QtCreator for Qt development > > > > > Am 10/12/2022 um 13:57 schrie

[Development] Heads up for anyone working on Qt Quick Controls code

Some directories have been renamed in this patch that will hopefully be merged soon: https://codereview.qt-project.org/c/qt/qtdeclarative/+/444028 You may have to rebase open patches. It may also be necessary to wipe your qtdeclarative build and rebuild. No user-facing API/libraries should be

Re: [Development] Duplicated test data tags

> -Original Message- > From: Edward Welbourne > Sent: Friday, 14 October 2022 4:56 PM > To: Milian Wolff ; EXT Mitch Curtis > Cc: Development@qt-project.org > Subject: Re: [Development] Duplicated test data tags [...] > Mitch Curtis (14 October 2022 03:4

Re: [Development] Duplicated test data tags

> -Original Message- > From: Development On Behalf Of > Milian Wolff > Sent: Friday, 14 October 2022 3:00 AM > To: Development@qt-project.org > Subject: Re: [Development] Duplicated test data tags > [...] > I have many times accidentally written bogus code that duplicated the tags. > Get

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

> -Original Message- > From: Development On Behalf Of > Volker Hilsheimer via Development > Sent: Monday, 10 October 2022 5:55 PM > To: development@qt-project.org > Subject: [Development] Using '#pragma once' instead of include guards? > > Hi, > > > We are using `#pragma once` in a numb

Re: [Development] Requesting a repository for Qt Quick Effect Maker

I asked this back in April but there was no official answer at that stage: what will the license be? From: Development On Behalf Of Tomi Korpipää Sent: Wednesday, 21 September 2022 6:56 PM To: development@qt-project.org Subject: Re: [Development] Requesting a repository for Qt Quick Effect Make

Re: [Development] Reminder: Codereview scheduled maintenance break on Monday 6-Jun 7 am CET

> -Original Message- > From: Development On Behalf Of > Thiago Macieira > Sent: Wednesday, 13 July 2022 23:43 PM > To: development@qt-project.org > Subject: Re: [Development] Reminder: Codereview scheduled maintenance > break on Monday 6-Jun 7 am CET > > On Monday, 6 June 2022 09:02:07 PD

Re: [Development] "error: ran out of registers during register allocation" when building qlibrary.cpp on macOS 11.6 with Clang 13

: Re: [Development] "error: ran out of registers during register > allocation" when building qlibrary.cpp on macOS 11.6 with Clang 13 > > On Monday, 22 November 2021 05:47:04 PST Mitch Curtis wrote: > > error: ran out of registers during register allocation > > Unless it

Re: [Development] Importing a module build in creator

This is the same situation I’m in. Would be nice if they were built when you hit run, but as a workaround I use Alt+B, Alt+R (from memory… I think that’s right): https://codereview.qt-project.org/c/qt-creator/qt-creator/+/330075 That way you can do that key combination and then Ctrl+R to run the

[Development] "error: ran out of registers during register allocation" when building qlibrary.cpp on macOS 11.6 with Clang 13

I'm running into the following error on macOS 11.6 with Clang 13: [577/1574] Building CXX object src/corelib/CMakeFiles/Core.dir/plugin/qlibrary.cpp.o FAILED: src/corelib/CMakeFiles/Core.dir/plugin/qlibrary.cpp.o /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/b

Re: [Development] Proposing to move deploy tools to qtbase

> -Original Message- > From: Development On Behalf Of > Ulf Hermann > Sent: Tuesday, 16 November 2021 3:23 PM > To: development@qt-project.org > Subject: Re: [Development] Proposing to move deploy tools to qtbase > > > I’m working on adding new CMake APIs for install support for Qt 6.3. >

Re: [Development] Jira and issues left "In Progress"

> -Original Message- > From: Development On Behalf Of > Alex Blasche > Sent: Thursday, 28 October 2021 3:45 PM > To: development@qt-project.org > Subject: [Development] Jira and issues left "In Progress" > > Hi, > > We have a growing problem with Jira issues forgotten in the "In Progress

Re: [Development] Nominating Oliver Eftevaag as Approver

+1 From: Development On Behalf Of Paul Wicking Sent: Wednesday, 27 October 2021 6:25 AM To: development@qt-project.org Subject: [Development] Nominating Oliver Eftevaag as Approver Hi all, I'd like to nominate Oliver Eftevaag as an approver. Oliver has been working as a software engineer for

[Development] qtquickcalendar's dev branch is now CMake-only

Hi. As part of porting qtquickcalendar to Qt 6 [1], and as done for "proper" Qt modules, CMake will now be the only supported build system with which to build the dev branch of the module. It is still possible to use the dev branch of qtquickcalendar in your qmake-based projects, and the 5.15 b

Re: [Development] Temporarily preventing changes being staged in the dev branch of qtquickcontrols2

0 pm, "Development on behalf of Mitch Curtis" wrote: > >Hi. > >I'd like to request that we temporarily prevent changes from being staged in the dev branch of qtquickcontrols2 in preparation for merging it into qtdeclarative, as otherwise ch

Re: [Development] Temporarily preventing changes being staged in the dev branch of qtquickcontrols2

CCing qt.relea...@qt.io since apparently the other address is no longer in use. On 20/7/21, 2:10 pm, "Development on behalf of Mitch Curtis" wrote: Hi. I'd like to request that we temporarily prevent changes from being staged in the dev branch of qtquickcontrols2

[Development] Temporarily preventing changes being staged in the dev branch of qtquickcontrols2

Hi. I'd like to request that we temporarily prevent changes from being staged in the dev branch of qtquickcontrols2 in preparation for merging it into qtdeclarative, as otherwise changes could be missed in the merge. I'm sending this to both the release team and the development mailing list as

Re: [Development] Mirror IRC channels on KDE's Matrix Instance

Hi Cristián, thanks for setting it up. I've never used Matrix before - how do I sign in using my KDE identity (I'm using the Element client if it makes a difference)? I'm guessing I need to set the homeserver to some KDE server? Cheers. > -Original Message- > From: Development On Beha

Re: [Development] Merging qtquickcontrols2 into qtdeclarative

Thanks Tor Arne. Can you elaborate a bit on the commands used for a prefixed subtree merge? Or point to a page that explains it? From: Tor Arne Vestbø Sent: Monday, 12 July 2021 4:17 PM To: Mitch Curtis Cc: development@qt-project.org Subject: Re: [Development] Merging qtquickcontrols2 into

[Development] Merging qtquickcontrols2 into qtdeclarative

Hi. The consensus from the contributor's summit session regarding https://bugreports.qt.io/browse/QTBUG-79454 was that qtquickcontrols2 should be merged into qtdeclarative: https://wiki.qt.io/QtCS2021_-_Testing_upstream_changes_with_downstream_modules#Move_specific_modules_into_the_repository_o

Re: [Development] Version-controlling the SVGs of built-in icons

> -Original Message- > From: Development On Behalf Of > Edward Welbourne > Sent: Friday, 18 June 2021 1:28 PM > To: Volker Hilsheimer > Cc: development@qt-project.org > Subject: Re: [Development] Version-controlling the SVGs of built-in icons > > Volker Hilsheimer (18 June 2021 11:19) wr

Re: [Development] Version-controlling the SVGs of built-in icons

For completeness since Alessandro mentioned exporting: for qtquickcontrols2, I've been using the same Inkscape extension that we document for exporting 9-patch images, since it also works with regular images: https://doc.qt.io/qt-5/qtquickcontrols2-imagine.html#exporting-9-patch-images From: De

Re: [Development] Version-controlling the SVGs of built-in icons

> -Original Message- > From: Development On Behalf Of > Volker Hilsheimer > Sent: Friday, 18 June 2021 11:20 AM > To: development@qt-project.org > Subject: [Development] Version-controlling the SVGs of built-in icons > > Hi, > > > The majority of time spent on QTBUG-38776 is chasing dow

Re: [Development] Solutions for ensuring that changes in upstream modules are tested with downstream modules before merging

From: Development On Behalf Of Shawn Rutledge Sent: Tuesday, 15 June 2021 10:57 PM To: development@qt-project.org Subject: Re: [Development] Solutions for ensuring that changes in upstream modules are tested with downstream modules before merging On 2021 Jun 7, at 15:30, Mitch Curtis

Re: [Development] Solutions for ensuring that changes in upstream modules are tested with downstream modules before merging

wasting developer time). Though then you do lose the ability to use controls in examples, which does seem like a huge loss. From: David Skoland Sent: Monday, 7 June 2021 1:30 PM To: Mitch Curtis Cc: Volker Hilsheimer ; development@qt-project.org Subject: Re: [Development] Solutions for ensuring that

Re: [Development] Solutions for ensuring that changes in upstream modules are tested with downstream modules before merging

r examples. From: Tuukka Turunen Sent: Friday, 4 June 2021 9:35 PM To: Volker Hilsheimer ; Mitch Curtis Cc: development@qt-project.org Subject: Re: [Development] Solutions for ensuring that changes in upstream modules are tested with downstream modules before merging Hi, Having the contr

Re: [Development] Solutions for ensuring that changes in upstream modules are tested with downstream modules before merging

> -Original Message- > From: Volker Hilsheimer > Sent: Friday, 4 June 2021 4:51 PM > To: Mitch Curtis > Cc: development@qt-project.org > Subject: Re: [Development] Solutions for ensuring that changes in upstream > modules are tested with downstream modules before me

Re: [Development] Solutions for ensuring that changes in upstream modules are tested with downstream modules before merging

> -Original Message- > From: Volker Hilsheimer > Sent: Friday, 4 June 2021 2:45 PM > To: Mitch Curtis > Cc: development@qt-project.org > Subject: Re: [Development] Solutions for ensuring that changes in upstream > modules are tested with downstream modules before me

[Development] Solutions for ensuring that changes in upstream modules are tested with downstream modules before merging

Hi. A common problem I see is that a change in say qtbase or qtdeclarative can cause test failures in modules that depend on them after that change is merged. As a result, dependency updates for the downstream modules can be blocked, requiring the module maintainer to look into the failure, onl

[Development] Stepping down as Qt Virtual Keyboard maintainer

Hi. I would like to formally step down as the maintainer of Qt Virtual Keyboard. I initially volunteered to take care of the module, however, with Jarkko Koivikko having written most of the module himself, it was never really an accurate reflection of its ownership. I have mostly been reviewing

[Development] Nominating Jarkko Koivikko as an approver

Hi. I would like to nominate Jarkko Koivikko as an approver for the Qt Project. Jarkko has been contributing to the Qt project since mid-2014, having practically written the entirety of the Qt Virtual Keyboard module. His knowledge in this area is second to none, and would be a great asset in

Re: [Development] Long-lived P1 issues

> -Original Message- > From: Development On Behalf Of > Jason McDonald > Sent: Friday, 4 December 2020 5:25 AM > To: Kai Köhne > Cc: development@qt-project.org > Subject: Re: [Development] Long-lived P1 issues > > > On Fri, 4 Dec 2020 at 02:09, Kai Köhne > wro

Re: [Development] Maintainers, your action needed: Qt 5.12.10 changes files

> -Original Message- > From: Development On Behalf Of > Jani Heikkinen > Sent: Friday, 16 October 2020 10:53 AM > To: development@qt-project.org > Subject: [Development] Maintainers, your action needed: Qt 5.12.10 changes > files > > Hi, > Initial ones here: https://codereview.qt- > proje

Re: [Development] qmake: qmltest missing in Qt6

> -Original Message- > From: Development On Behalf Of > Arno Rehn > Sent: Sunday, 9 August 2020 7:58 PM > To: development@qt-project.org > Subject: [Development] qmake: qmltest missing in Qt6 > > Hey everybody, > > I'm trying to port over qtwebchannel from qmake to CMake, so we can > hop

Re: [Development] Requesting a repository for Qt Quick Calendar

https://bugreports.qt.io/browse/QTQAINFRA-3812 > -Original Message- > From: Edward Welbourne > Sent: Wednesday, 24 June 2020 11:33 AM > To: Mitch Curtis > Cc: development@qt-project.org > Subject: Re: Requesting a repository for Qt Quick Calendar > > Mitch Cu

Re: [Development] Requesting a repository for Qt Quick Calendar

-Original Message- > From: Development On Behalf Of > Mitch Curtis > Sent: Wednesday, 17 June 2020 9:00 AM > To: development@qt-project.org > Subject: [Development] Requesting a repository for Qt Quick Calendar > > Hi. > > I'd like to request a Ge

[Development] Requesting a repository for Qt Quick Calendar

Hi. I'd like to request a Gerrit repository for Qt Quick Calendar at qt/qtquickcalendar. The Qt Quick Calendar module provides a set of types that can be used to build calendars in Qt Quick. This module will be delivered through the marketplace. It will be released independently of Qt release

Re: [Development] Proposal: Deprecate QVector in Qt 6

> -Original Message- > From: Development On Behalf Of > André Somers > Sent: Thursday, 23 April 2020 12:04 PM > To: Jaroslaw Kobus ; development@qt-project.org > Subject: Re: [Development] Proposal: Deprecate QVector in Qt 6 > > Hi, > > On 23-04-20 11:58, Jaroslaw Kobus wrote: > > There

Re: [Development] Priority field in Jira

>From: Volker Hilsheimer > > The priority field changes it’s meaning during the lifetime of the bug report: > > * in the beginning, it tells us how important it is for the reporter of the > bug. This is useful. This is news to me; I've not once heard of it being used this way. I also question

Re: [Development] Priority field in Jira

> >From: Development on behalf of Lorn >Potter >Sent: Wednesday, 26 February 2020 11:15 AM >To: development@qt-project.org >Subject: Re: [Development] Priority field in Jira > >On 25/2/20 8:11 PM, Joerg Bornemann wrote: >> On 2/25/20 10:31, Edward Welbourn

Re: [Development] Priority field in Jira

Will try to make comments inline... had to change email client. On 25/2/20, 10:31 am, "Edward Welbourne" wrote: Mitch Curtis (25 February 2020 10:23) elaborated on what he'd said earlier: >> For some context and for those who don't know: within the company,

Re: [Development] Priority field in Jira

> For some context and for those who don't know: within the company, we > now have weekly bug triaging where a team of two people prioritise all > unprioritised bugs. So new reports rarely go more than a few days without > having a priority set. We've been doing this for a few years (?) now and it

[Development] Priority field in Jira

Hi. I'm curious about what the reasons were for allowing (non-approver) reporters of bugs to set the priority field in Jira. In my experience this often results in priorities being assigned that don't follow our conventions [1] on what constitutes a certain priority, but instead a priority tha

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default

> -Original Message- > From: Edward Welbourne > Sent: Monday, 24 February 2020 1:35 PM > To: Mitch Curtis > Cc: Qt development mailing list ; Lars Knoll > ; Thiago Macieira > Subject: Re: [Development] A modest proposal: disable lower-case > keywords (emit, f

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default

> -Original Message- > From: Lars Knoll > Sent: Monday, 24 February 2020 1:40 PM > To: Mitch Curtis > Cc: Thiago Macieira ; Qt development mailing > list > Subject: Re: [Development] A modest proposal: disable lower-case > keywords (emit, foreach, forever, si

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default

> -Original Message- > From: Development On Behalf Of > Ville Voutilainen > Sent: Friday, 21 February 2020 3:02 PM > To: Christian Kandeler > Cc: development@qt-project.org > Subject: Re: [Development] A modest proposal: disable lower-case > keywords (emit, foreach, forever, signals, slot

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default

> -Original Message- > From: Development On Behalf Of > Lars Knoll > Sent: Monday, 24 February 2020 12:25 PM > To: Thiago Macieira > Cc: Qt development mailing list > Subject: Re: [Development] A modest proposal: disable lower-case > keywords (emit, foreach, forever, signals, slots) by d

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default

default > > > > On 21 Feb 2020, at 13:30, Mitch Curtis wrote: > > How can you tell if it's a signal being emitted or just a function call > > without > the emit syntax? With the emit syntax before the signal emission, it's > immediately obvious that

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default

> -Original Message- > From: Eike Ziller > Sent: Friday, 21 February 2020 1:55 PM > To: Mitch Curtis > Cc: Ville Voutilainen ; Alex Blasche > ; development@qt-project.org > Subject: Re: [Development] A modest proposal: disable lower-case > keywords (emit, foreach,

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default

> -Original Message- > From: Eike Ziller > Sent: Friday, 21 February 2020 1:55 PM > To: Mitch Curtis > Cc: Ville Voutilainen ; Alex Blasche > ; development@qt-project.org > Subject: Re: [Development] A modest proposal: disable lower-case > keywords (emit, foreach,

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default

> -Original Message- > From: Ville Voutilainen > Sent: Friday, 21 February 2020 1:42 PM > To: Mitch Curtis > Cc: Alex Blasche ; development@qt-project.org > Subject: Re: [Development] A modest proposal: disable lower-case > keywords (emit, foreach, forever, signa

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default

> -Original Message- > From: Development On Behalf Of > Ville Voutilainen > Sent: Friday, 21 February 2020 12:16 PM > To: Alex Blasche > Cc: development@qt-project.org > Subject: Re: [Development] A modest proposal: disable lower-case > keywords (emit, foreach, forever, signals, slots) by

Re: [Development] [Releasing] HEADS-UP: Qt 5.15 Feature Freeze is in effect now

> -Original Message- > From: Releasing On Behalf Of Jani > Heikkinen > Sent: Wednesday, 5 February 2020 6:37 AM > To: Lars Knoll ; Yulong Bai > Cc: Volker Hilsheimer ; Qt development mailing list > ; releas...@qt-project.org > Subject: Re: [Releasing] [Development] HEADS-UP: Qt 5.15 Featu

Re: [Development] The future of smart pointers in Qt API

> Vitaly Fanaskov > > [...] In this case, I think we won't have this confusing definitions like > "visual > parent" and "just a parent" > (that we have in controls). Sorry, couldn't resist: visual parent vs QObject parent is a distinction that Qt Quick made, not Qt Quick Controls.

Re: [Development] Notes from "Releasing" session in QtCon19

> -Original Message- > From: Development On Behalf Of > André Hartmann > Sent: Saturday, 23 November 2019 2:02 PM > To: Christian Ehrlicher ; development@qt- > project.org > Subject: Re: [Development] Notes from "Releasing" session in QtCon19 > > Hi all, > > > The script creating the cha

Re: [Development] clang-format

> -Original Message- > From: Development On Behalf Of > Frederik Gladhorn > Sent: Monday, 14 October 2019 1:46 PM > To: development@qt-project.org > Subject: [Development] clang-format > > Hi, > > after just a bit over a year, we have a hint of progress on the state of using > clang-form

Re: [Development] Property bindings in Qt 6

> -Original Message- > From: Development On Behalf Of > Simon Hausmann > Sent: Thursday, 26 September 2019 5:03 PM > To: development@qt-project.org > Subject: [Development] Property bindings in Qt 6 > > Hi, > > Earlier this year, Olivier, Samuel, Auri and I worked on a project to re- > e

Re: [Development] Question about tests/manual folders

> -Original Message- > From: Development On Behalf Of > Asmo Saarela > Sent: Friday, 20 September 2019 8:30 AM > To: development@qt-project.org > Subject: [Development] Question about tests/manual folders > > Hi all, > > > > I would like to understand the content and the use of the man

Re: [Development] Qt Static Package

> -Original Message- > From: Simon Hausmann > Sent: Monday, 29 April 2019 5:58 PM > To: Mitch Curtis > Cc: Thiago Macieira ; development@qt- > project.org > Subject: Re: [Development] Qt Static Package > > > The application is perfectly distributable, but

Re: [Development] Qt Static Package

> -Original Message- > From: Development On Behalf Of > Mitch Curtis > Sent: Monday, 29 April 2019 5:45 PM > To: Thiago Macieira ; development@qt- > project.org > Subject: Re: [Development] Qt Static Package > > > -Original Message- > &g

Re: [Development] Qt Static Package

> -Original Message- > From: Development On Behalf Of > Thiago Macieira > Sent: Monday, 29 April 2019 5:18 PM > To: development@qt-project.org > Subject: Re: [Development] Qt Static Package > > On Monday, 29 April 2019 00:27:14 PDT Mitch Curtis wrote: &g

Re: [Development] Qt Static Package

> -Original Message- > From: Carlos Enrique Pérez Sánchez > Sent: Friday, 26 April 2019 9:42 PM > To: Mitch Curtis ; development@qt-project.org > Subject: Re: [Development] Qt Static Package > > > This sounds very similar to what I saw with linuxdeployqt a while

Re: [Development] Qt Static Package

> -Original Message- > From: Development On Behalf Of > Carlos Enrique Pérez Sánchez > Sent: Saturday, 20 April 2019 2:56 AM > To: development@qt-project.org > Subject: Re: [Development] Qt Static Package > > I invited Mitch Curtis to join the discussion. He

Re: [Development] A deployment tool for Linux

ynamically linked like ICU) or using linuxdeployqt, and I only bother supporting Ubuntu because that's what I use. On 4/10/19, 8:35 PM, "André Pönitz" wrote: On Wed, Apr 10, 2019 at 08:13:01AM +, Mitch Curtis wrote: > What do people think about having a deploymen

Re: [Development] A deployment tool for Linux

dea to have an official deployment tool as we > > have for windows. linuxdeployqt works but as mentioned earlier slower > and older. > > The things can get a bit better. Regards,Khuram Ali > > > > > > -Ursprüngliche Mitteilung- > > Von: Mitch Curt

Re: [Development] A deployment tool for Linux

> -Original Message- > From: Bogdan Vatra > Sent: Wednesday, 10 April 2019 10:22 AM > To: development@qt-project.org > Cc: Mitch Curtis > Subject: Re: [Development] A deployment tool for Linux > > Hi, > > Personally I think it's a great idea.

[Development] A deployment tool for Linux

What do people think about having a deployment tool for Linux? There is an existing community tool based on macdeployqt: https://github.com/probonopd/linuxdeployqt/ The author has considered the idea in the past: https://github.com/probonopd/linuxdeployqt/issues/84 A Jira suggestion to track i

Re: [Development] Supporting helper functions in auto tests by providing throwing Qt Test macros

> -Original Message- > From: Giuseppe D'Angelo > Sent: Friday, 5 April 2019 12:39 AM > To: Mitch Curtis ; development@qt-project.org > Subject: Re: [Development] Supporting helper functions in auto tests by > providing throwing Qt Test macros > > Il 03

Re: [Development] Supporting helper functions in auto tests by providing throwing Qt Test macros

> -Original Message- > From: Edward Welbourne > Sent: Thursday, 4 April 2019 10:51 AM > To: Mitch Curtis > Cc: development@qt-project.org; Joerg Bornemann > > Subject: Re: [Development] Supporting helper functions in auto tests by > providing throwing Qt Test macr

Re: [Development] Supporting helper functions in auto tests by providing throwing Qt Test macros

> -Original Message- > From: Edward Welbourne > Sent: Wednesday, 3 April 2019 5:07 PM > To: Mitch Curtis > Cc: development@qt-project.org; Joerg Bornemann > > Subject: Re: [Development] Supporting helper functions in auto tests by > providing throwing Qt Test ma

Re: [Development] Supporting helper functions in auto tests by providing throwing Qt Test macros

n Tue, Apr 2, 2019, at 5:17 PM, Mitch Curtis wrote: > > Quoting the commit message here: > > > > WIP: Add _THROW variants to testlib macros > > > > This allows using Qt Test macros in helper functions, avoiding the need > > to write a lot of boilerplat

Re: [Development] Supporting helper functions in auto tests by providing throwing Qt Test macros

Resending to the list... > -Original Message- > From: Mitch Curtis > Sent: Wednesday, 3 April 2019 1:58 PM > To: 'Giuseppe D'Angelo' > Subject: RE: [Development] Supporting helper functions in auto tests by > providing throwing Qt Test macros > >

Re: [Development] Supporting helper functions in auto tests by providing throwing Qt Test macros

> -Original Message- > From: Edward Welbourne > Sent: Wednesday, 3 April 2019 12:07 PM > To: Joerg Bornemann ; Mitch Curtis > > Cc: development@qt-project.org > Subject: Re: [Development] Supporting helper functions in auto tests by > providing throwing Qt Test ma

Re: [Development] Supporting helper functions in auto tests by providing throwing Qt Test macros

> -Original Message- > From: Joerg Bornemann > Sent: Wednesday, 3 April 2019 9:55 AM > To: Mitch Curtis ; development@qt-project.org > Subject: Re: [Development] Supporting helper functions in auto tests by > providing throwing Qt Test macros > > On 4/2/19 5:1

[Development] Supporting helper functions in auto tests by providing throwing Qt Test macros

As described in https://bugreports.qt.io/browse/QTBUG-66320, currently Qt users are on their own if they want to call helper functions that can fail a test. The reason is documented: Note: This macro can only be used in a test function that is invoked by the test framework. A common workar

Re: [Development] Switching from create_changelog.pl to createchangelog for change log generation

> > On 2 Apr 2019, at 11:40, Mitch Curtis wrote: > > ... > > So, the end result of switching to this is that it becomes clearer that we > > are > actually fixing (non-trivial) bugs, contrary to what the "only minor code > improvements" message says. Yes, it

[Development] Switching from create_changelog.pl to createchangelog for change log generation

Currently change files are generated using create_changelog.pl from qtsdk.git [1]. This works OK, but misses a lot of bug fixes. For example, the 5.12.3 release of Qt Quick Controls 2 has a bunch of fixes, but create_changelog.pl still results in the "This release contains only minor code improv

Re: [Development] Qt Quick Templates 2 from C++

I'm mostly going off what JP had in mind, which are the following: - https://bugreports.qt.io/browse/QTBUG-67062: Add full/public theming support for QQC2 styles - https://bugreports.qt.io/browse/QTBUG-73944: Make QQuickControl public - https://bugreports.qt.io/browse/QTBUG-66829: Add IconImage t

Re: [Development] QtQuick.Layouts and content margins

> -Original Message- > From: Development On Behalf Of > Alberto Mardegan > Sent: Monday, 25 February 2019 1:05 PM > To: development@qt-project.org > Subject: Re: [Development] QtQuick.Layouts and content margins > > On 25/02/19 11:23, Mitch Curtis wrote: > &

Re: [Development] QtQuick.Layouts and content margins

> -Original Message- > From: Development On Behalf Of > Alberto Mardegan > Sent: Sunday, 24 February 2019 12:29 PM > To: development@qt-project.org > Subject: [Development] QtQuick.Layouts and content margins > > Hi there! > I'm working on a desktop style for QtQuick.Controls 2 [1], a

Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files

> -Original Message- > From: Development On Behalf Of > Shawn Rutledge > Sent: Thursday, 21 February 2019 1:45 PM > To: development@qt-project.org > Subject: Re: [Development] Maintainers, your action needed: Qt 5.12.2 > changes files > > > > On 21 Feb 2019, at 12:47, Cristián Maureira-F

Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files

> -Original Message- > From: Cristián Maureira-Fredes > Sent: Thursday, 21 February 2019 12:47 PM > To: Mitch Curtis ; Jani Heikkinen ; > development@qt-project.org > Subject: Re: [Development] Maintainers, your action needed: Qt 5.12.2 > changes files > > H

Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files

> -Original Message- > From: Jani Heikkinen > Sent: Thursday, 21 February 2019 11:06 AM > To: Mitch Curtis ; development@qt-project.org > Subject: RE: [Development] Maintainers, your action needed: Qt 5.12.2 > changes files > > > -Original Message- >

Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files

> -Original Message- > From: Development On Behalf Of > Mitch Curtis > Sent: Thursday, 21 February 2019 9:33 AM > To: Jani Heikkinen ; development@qt-project.org > Subject: Re: [Development] Maintainers, your action needed: Qt 5.12.2 > changes files > &

Re: [Development] Maintainers, your action needed: Qt 5.12.2 changes files

> -Original Message- > From: Development On Behalf Of > Jani Heikkinen > Sent: Thursday, 21 February 2019 9:19 AM > To: development@qt-project.org > Subject: [Development] Maintainers, your action needed: Qt 5.12.2 changes > files > > Hi, > Initial ones here: https://codereview.qt- > proj

  1   2   3   >