Re: [Development] Why does QQuickImageProvider not support SVG images?

> On Mar 12, 2025, at 09:46, Schimkowitsch Robert > wrote: > > Hi, > I immediately jumped on the brand-new VectorImage, and quickly found, to my > disappointment, that I cannot use it, because I am missing an important piece. > How am I supposed to pass a memory-generated SVG via URL? > Norm

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

I’m nominating Oliver Eftevaag as the maintainer of Qt Quick Dialogs. He was instrumental in the process of rewriting the old version to use Qt Quick Controls 2 and refining the API that the dialogs now have; and he has been acting as the de-facto maintainer since then. You can see his patches

Re: [Development] RFC: Scriptable Widgets

> On Nov 28, 2024, at 09:08, Fabian Kosmale via Development > wrote: > - Some are already (indirectly) exposed via Q_PROPERTY; should anyone decide > to expose those Widgets to QML (or some other language binding working on the > meta-object system), this would cause some friction because ther

Re: [Development] On Removing Public Undocumented/\internal APIs

On Mar 13, 2024, at 12:30 AM, Marc Mutz via Development wrote: TL;DR: Make qdoc openly document \internal members of documented classes/namespaces or defined in public headers as "Internal. Subject to change without notice. If you feel this function should be public, file a bug report with your

Re: [Development] Nominating Matthias Rauter for approval status

On Jan 30, 2024, at 5:11 AM, Paul Tvete via Development wrote: Hi, I would like to nominate Matthias Rauter as an approver for the Qt Project. +1 -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

Re: [Development] Marking the Tech Preview APIs as such

On Jan 22, 2024, at 10:41 AM, Giuseppe D'Angelo via Development wrote: Hi, A number of classes and functions that are going to be introduced in 6.7 are meant to be "tech preview", and thus they may pass the header review even if we are aware of some limitations or issues with their design.

Re: [Development] New assign() Functionality Added to Qt Containers

Sounds efficient. What is the meaning of the tilde the way you are using it here in operator=(~) ? > On 6 Sep 2023, at 11:30, Dennis Oberst via Development > wrote: > > Hello everyone, > > I would like to inform you that we've added assign(~) functionality to the > following > Qt containers:

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

+1 On 20 Jun 2023, at 20:55, Jan-Arve Sæther via Development wrote: Hello all, I would like to nominate Santhosh Kumar Selvaraj for approver rights in the Qt project. Santhosh is a member of the UI Team, and has been working on improvement to our styles, dark mode support, palette handling

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

> 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 bo

Re: [Development] libQt6Core.so links against both libpcre.so.3 and libpcre2-16.so.0

On 8 Mar 2023, at 11:42, Shawn Rutledge via Development wrote: My developer build: $ lddtree /zhome/rutledge/dev/qt6-dbg/qtbase/lib/libQt6Core.so.6.2.0 Oops that was an old leftover; anyway it looks about the same in current dev branch: /home/rutledge/dev/qt6-dbg/qtbase/lib/libQt6Core.so

Re: [Development] libQt6Core.so links against both libpcre.so.3 and libpcre2-16.so.0

> On 8 Mar 2023, at 11:16, Marc Mutz via Development > wrote: > > Hi, > > Did my first conscious ldd on QtCore todays and just found it curious > that it linked against pcre and pcre2-16. > > Digging, I found that the pcre dep gets dragged in by glib-2.0: > > objdump -p /usr/lib/x86_64-l

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

On 3 Feb 2023, at 13:56, Tuukka Turunen via Development wrote: pdf/pdfviewer Depends which one you mean. They are all new and maintained at this point. There is some redundancy on purpose, because there are multiple PDF-viewing components. So I wouldn’t delete any of them. quick/delegate

Re: [Development] CMake UNITY_BUILD ( QTBUG-109394 )

> On 16 Jan 2023, at 13:49, Friedemann Kleint via Development > wrote: > > Hi, > > I would like to propose considering making Qt suitable for CMake UNITY_BUILDs > ( https://bugreports.qt.io/browse/QTBUG-109394 , > https://cmake.org/cmake/help/latest/prop_tgt/UNITY_BUILD.html ) . > > This ha

Re: [Development] Nominating Axel Spoerl as approver

+1 I’m impressed with his lack of fear to dig into unfamiliar code to fix old and stubborn bugs, and optimistic attitude. > 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 bee

Re: [Development] Renaming quint128

On 2022 Nov 18, at 03:13, Thiago Macieira mailto:thiago.macie...@intel.com>> wrote: I was working on extended integers and added qint128 and quint128 to qglobal.h Interesting. How far can we go with doubling bits? quint512 in case you have AVX-512 registers? (I must get a laptop with that f

Re: [Development] Adding CPD support to Qt print dialog

On 2022 Sep 26, at 16:54, Volker Hilsheimer mailto:volker.hilshei...@qt.io>> wrote: I think it will be easier to understand what abstraction we need once we have a patch to look at that implements CPDB support. That we don’t have a QPA-level abstraction for print dialogs in Qt shouldn’t block

Re: [Development] Nominating Christian Ehrlicher and Andy Shaw as Qt SQL co-maintainers

+1 It’s good to have active maintainers. > On 2022 Sep 26, at 09:11, Volker Hilsheimer wrote: > > Hi, > > > I would like to nominate Christian and Andy as co-maintainers for Qt SQL. > > Mark Brand, who is currently listed as the maintainer of Qt SQL, hasn’t > responded to any of my emails,

Re: [Development] Redesigning QML value types

> On 2022 Sep 21, at 14:59, Ulf Hermann wrote: > > Thanks for the feedback! I've thought about it some more and done some > experiments and I think we can solve this in a way that makes everyone happy: > > If a function has type annotations, we pass its arguments and return value by > value (

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

Yes! I’m looking forward to having that public. On 2022 Sep 21, at 12:55, Tomi Korpipää mailto:tomi.korpi...@qt.io>> wrote: Anyone to second this? -Tomi From: Volker Hilsheimer mailto:volker.hilshei...@qt.io>> Sent: Wednesday, August 31, 2022 11:43 To: Tomi Kor

Re: [Development] Adding CPD support to Qt print dialog

On 2022 Sep 19, at 12:38, Till Kamppeter mailto:till.kamppe...@gmail.com>> wrote: On 16/09/2022 08:32, Shawn Rutledge wrote: But Qt has its own D-Bus implementation, so we tend to prefer using that, rather than using some external library that uses some other library that talks to

Re: [Development] Adding CPD support to Qt print dialog

gt; Subject: Re: [Development] Adding CPD support to Qt print dialog On Fri, 16 Sep 2022 06:32:38 + Shawn Rutledge mailto:shawn.rutle...@qt.io>> wrote: > Another aspect that I haven’t kept up with very well is how > containerized applications should do printing. We have “portal”

Re: [Development] Adding CPD support to Qt print dialog

On 2022 Sep 16, at 00:20, Gaurav Guleria mailto:gaurav.g...@gmail.com>> wrote: Hello all, I am Gaurav Guleria, a GSoC student, working with Till Kamppeter to add and improve Common Print Dialog (CPD) support to existing print dialogs like GTK and Qt. More about CPD can be read here: https:/

Re: [Development] Nominating David and Eskil as Qt Wayland maintainers

> On 2022 Aug 24, at 10:36, Volker Hilsheimer wrote: > > I’d like to nominate David Edmundson (davidedmund...@kde.org) as the > maintainer of the Qt Wayland Client module, and Eskil Abrahamsen Blomfeld > (eskil.abrahamsen-blomfe...@qt.io) as the maintainer of the Qt Wayland > Compositor modul

Re: [Development] Stickman animation example removed from qtbase in Qt 6

On 2022 Aug 17, at 09:57, Rasool, Ansar mailto:ansar_ras...@mentor.com>> wrote: Hi All, It seems that Stickman and many other widget animation examples from qtbase has been removed in Qt6 as compared to Qt5. Is there any particular reason behind the removal of these examples? They were mov

Re: [Development] Proposing to add (CPU) architecture maintainers

I would like to get more familiar with RISC-V when I’ve got hardware for it, and might consider volunteering then. (I don’t have any Qt-capable hardware yet, only the U540 microcontroller; but better stuff is starting to become available actually.) As for POWER I do occasionally test on Debian

Re: [Development] QPushButton: drag and drop

> On 2022 Jun 3, at 23:05, Volker Hilsheimer wrote: > > This is of course a special case, but it shows that we can’t just start > delivering MouseButtonRelease events to widgets when a drag operation > finishes, because they would suddenly execute mouseReleaseEvent code in a > state in which

Re: [Development] Do we have some plans about the damage tracking of QtQuick's scene graphics?

On 2022 Jun 2, at 11:47, 弓 长 mailto:zc...@live.com>> wrote: I am doing a Wayland compositor use the QtQuick with wlroots, when the client's window has update its buffer, I had to update the whole screen, usually the dirty area would be small, but this is only possible in QtQuick. https://bugr

Re: [Development] Leaving The Qt Company

I was really surprised to hear that you are leaving, but it’s good that you will still be around. It must have been an amazing experience to start a new web browser in those days. I still think QTextDocument and its related classes and views have relevance, even though today’s browsers left th

Re: [Development] QKeySequenceEdit questions

On 2022 May 18, at 11:21, Eike Ziller mailto:eike.zil...@qt.io>> wrote: We have several multiple-chord shortcuts in Qt Creator, at least for code pasting, test integration, version control system integration, and editor splitting/navigation. At some point the space for single chord shortcuts s

Re: [Development] Nominating Jonas Karlsson as maintainer for Qt Quick 3D Physics (and consequently for approver status)

+1 On 2022 May 12, at 10:12, Paul Tvete mailto:paul.tv...@qt.io>> wrote: Jonas has been working for the Qt Company since April 2020, and we somehow forgot to nominate him for approver status before now. He has been working on the Qt Quick 3D module, as part of the Oslo graphics team. His curr

Re: [Development] Request qtquickdesigner-components as Qt 6 addon

On 2022 May 5, at 16:23, Thomas Hartmann mailto:thomas.hartm...@qt.io>> wrote: Hi, I would like to request the inclusion of a new module to Qt 6 as an add-on: Name of the repository: qt-labs/qtquickdesigner-components Description: Module for Qt Design Studio specific QML items Responsible pers

Re: [Development] Nominating David Skoland as approver

+1 On 2022 Apr 21, at 14:00, Morten Sørvig mailto:morten.sor...@qt.io>> wrote: I'd like to nominate David Skoland as approver for the Qt Project. David is employed by the Qt company has been contributing to Qt since late 2020, with patches and reviews to several modules. He has recently shifte

Re: [Development] XCB platform plugin maintainer change

+1 He has been the defacto maintainer for a while now. On 2022 Feb 1, at 10:50, Gatis Paeglis mailto:gatis.paeg...@qt.io>> wrote: Hi all, I would like to propose a change in Qt's Linux/XCB maintainership. Since 2019, I have moved full time to the Qt for MCUs project and there is no time left f

Re: [Development] Nominating Volker Hilsheimer as co-maintainer of Qt Widgets

> On 2022 Jan 25, at 09:38, Richard Gustavsen wrote: > > Hi all! > > I would like to propose a change in the maintenance of Qt Widgets [1]. I’m > the current maintainer of the module, but I’m happy to inform you that Volker > Hilsheimer has agreed to join me as a co-maintainer. Volker is one

Re: [Development] Nominating Dimitrios "Jimis" Apostolou as Approver

> On 2022 Jan 19, at 12:59, Volker Hilsheimer wrote: > > Hi, > > I’d like to nominate Dimitrios Apostolou, aka Jimis, as approver in the Qt > Project. > > Jimis has been working as a Software Engineer in the Qt Company since 2019 > and has made a number of contributions [0] and reviews [1].

Re: [Development] Documentation of new Qt features in qtdoc

ChangeLog entries from the git log may often be badly-worded or be written badly for the audience that’s going to read them, but I think we should still start from those, for the sake of completeness. We can simply modify the tooling to output qdoc syntax instead of markdown. Then we'll end up

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

On 2021 Nov 16, at 12:06, EXT Craig Scott mailto:craig.sc...@qt.io>> wrote: I’m working on adding new CMake APIs for install support for Qt 6.3. As part of that, there will be conveniences for invoking the appropriate xxxdeployqt tool where available. At the moment, macdeployqt and windeployqt

Re: [Development] Nominating Doris Verria as Approver

+1 > On 2021 Oct 28, at 10:14, Jan-Arve Sæther wrote: > > +1 > > -Original Message- > From: Development On Behalf Of Volker > Hilsheimer > Sent: onsdag 27. oktober 2021 11:56 > To: development@qt-project.org > Subject: [Development] Nominating Doris Verria as Approver > > Hello World

Re: [Development] Nominating Oliver Eftevaag as Approver

+1 On 2021 Oct 27, at 06:25, Paul Wicking mailto:paul.wick...@qt.io>> wrote: Hi all, I'd like to nominate Oliver Eftevaag as an approver. Oliver has been working as a software engineer for the Qt Company for almost a year now and has made a fair number of contributions to Qt [0]. He also par

Re: [Development] Why clipping is enabled by default in QQuickTextField ?

I saw your comment on IRC a while after you had written it and left; see https://bugreports.qt.io/browse/QTBUG-97648 > On 2021 Oct 23, at 22:02, Murat ŞEKER via Development > wrote: > > Hello, > > We are investigating some performance issues and it turns out the clipping in > TextField ruins

Re: [Development] Feature freeze exception for QTBUG-95587

On 2021 Sep 13, at 20:58, Elvis Stansvik mailto:elvst...@gmail.com>> wrote: Yes, URLs are vital to QML I guess, but are they *that* vital? The bar should be quite high IMO. In the apps I've worked on, URLs and URL handling is really not central at all. We’re talking about potentially a lot of I

Re: [Development] Feature freeze exception for QTBUG-95587

> On 2021 Sep 9, at 17:32, Ulf Hermann wrote: > > A user can fix this by explicitly calling Qt.resolvedUrl() in order to > resolve the URL in a specific context and make it absolute. As we need URLs > rather often in QML, we will see much more Qt.resolvedUrl() in Qt6 than we > have seen in Q

Re: [Development] Do we need version tags in released src packages?

On 13 Aug 2021, at 13:39, Albert Astals Cid via Development mailto:development@qt-project.org>> wrote: It seems a bad idea to have files with the same name and the different contents. It can lead to all kind of confusion in which you download something, then "download the same file" 5 days lat

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

+1 ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

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

> On 2021 Jun 18, at 11:19, Volker Hilsheimer wrote: > > Hi, > > > The majority of time spent on QTBUG-38776 is chasing down the various SVGs > from which it’s then trivial to generate PNGs in different resolutions. > > Which makes me think that we should have those SVGs version controlled

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 mailto:mitch.cur...@qt.io>> wrote: Some I can think of: - Slower git operations. - Slower build times for qtdeclarative devs. You can use e.g. ninja targets, but you would have to do this every time you build. Ideally we’d add a configure option for this,

Re: [Development] Windows maintainer change

+1 Thanks for the work that all 3 of you have put into it over the years. > On 15 Jun 2021, at 09:27, Oliver Wolff wrote: > > Hi all, > > I would like to propose a change in Qt's Windows maintainership. I think that > everybody knows, that Friedemann has been doing a great job maintaining the

[Development] Gesture-scoped vs. "persistent" properties in pointer handlers; handlers in 3D

(The TLDR for this is https://bugreports.qt.io/browse/QTBUG-94168) When working on pointer handlers a few years ago, I was mainly thinking of the primary use cases where the target property points to an Item to be manipulated, and when the handler is active, it changes the appropriate propertie

Re: [Development] Moving IRC from Freenode to Libera.Chat, voting thread

> On 2021 May 22, at 03:06, Giuseppe D'Angelo via Development > wrote: > > Hi, > > As detailed in the other thread, I'd like to gather lazy consensus for moving > the official IRC presence from Freenode to Libera.Chat. > > Please use this thread for voting ONLY. Apologies for all the formal

Re: [Development] Changes to Freenode's IRC

> On 2021 May 19, at 18:21, Jason H wrote: > >> Hi! >> >> On Wed, 19 May 2021 at 12:30, Jason H wrote: >>> >>> Aren't all the kids these days moving to Discord? >> >> Discord is not free software, so it does not align well with a free >> software project. > > QtCentre is not free software >

Re: [Development] Changes to Freenode's IRC

On 2021 May 19, at 17:14, Carl Schwan mailto:c...@carlschwan.eu>> wrote: Le mercredi, mai 19, 2021 4:49 PM, Giuseppe D'Angelo via Development mailto:development@qt-project.org>> a écrit : On 19/05/2021 16:37, Andy Nichols wrote: Rather than just move to another IRC server, we should really t

Re: [Development] Qt 6.1.0 release note: let's use Markdown (again!)

> On 2021 Apr 28, at 14:38, Giuseppe D'Angelo via Development > wrote: > > Hi, > > Il 28/04/21 13:00, Shawn Rutledge ha scritto: >> What I was proposing last year on the mailing list is: let’s format the >> changelog in markdown, with proper links for t

Re: [Development] Qt 6.1.0 release note: let's use Markdown (again!)

On 2021 Apr 28, at 14:25, Jani Heikkinen mailto:jani.heikki...@qt.io>> wrote: Hi Shawn, First of all: sorry about getting you feel your efforts wasn't appreciated! I understand why you feel so but trust me, that hasn't been the case: We appreciate your help & your opinions; it is just that w

Re: [Development] Qt 6.1.0 release note: let's use Markdown (again!)

On 2021 Apr 28, at 11:11, Jani Heikkinen mailto:jani.heikki...@qt.io>> wrote: Giuseppe D'Angelo via Development Hi, On 27/04/2021 11:53, Jani Heikkinen wrote: Initial release note for Qt 6.1.0 here:https://code.qt.io/cgit/qt/qtreleasenotes.git/tree/qt/6.1.0/relea se-note.txt I must say, I d

Re: [Development] Nominating Andrei Golubev as Approver

> On 2021 Mar 18, at 15:00, Edward Welbourne wrote: > > I'd like to nominate Andrei Golubev as an Approver. +1 ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

[Development] Pointer handlers: transparent or block? was Re: QEvent::accept() vs. the newer event delivery algorithms in Qt Quick; remaining API issues; etc.

On 2020 Oct 8, at 13:26, Shawn Rutledge mailto:shawn.rutle...@qt.io>> wrote: If you subclass QQuickItem and start handling events, it becomes clear that QEvent::accept() has always meant two things in legacy Qt Quick: 1) stop propagation and 2) grab the mouse. …etc… and there weren’t

Re: [Development] Nominating Aleix Pol Gonzalez for approver status

On 2021 Feb 18, at 07:30, Eskil Abrahamsen Blomfeldt mailto:eskil.abrahamsen-blomfe...@qt.io>> wrote: Hi all! I would like to nominate Aleix Pol Gonzalez as an approver for the Qt Project. +1 ___ Development mailing list Development@qt-project.o

Re: [Development] Qt 6 co-installability with Qt 5

> On 2021 Feb 16, at 14:31, Kai Köhne wrote: > > Well, let's just realize that, by renaming qmake to qmake6 everywhere > (including in the documentation), we actually create some confusion for our > existing users, too. Also, I think adding version numbers to the name of > tools is just no go

Re: [Development] Qt 6.0.x releasing and Qt 6.0.x changes files

On 2020 Dec 1, at 10:00, Jani Heikkinen mailto:jani.heikki...@qt.io>> wrote: Hi all, Qt 6.0.0 should be out really soon and it is time to start planning upcoming patch level releases for the Qt 6.0 series. Plan is to release quick updates for the Qt 6.0 pretty much similarly than we did in th

Re: [Development] Making Binary Incompatible Changes after Qt 6.0

On 2021 Jan 27, at 16:56, Shawn Rutledge mailto:shawn.rutle...@qt.io>> wrote: touch->mouse synthesis (!) which is rarely used Of course I wrote that backwards: they tried to rely on mouse->touch synthesis, which is rarely used; and there’s more than one way to solve their use ca

Re: [Development] Making Binary Incompatible Changes after Qt 6.0

On 2021 Jan 27, at 16:39, Volker Hilsheimer mailto:volker.hilshei...@qt.io>> wrote: On 10 Dec 2020, at 09:48, Lars Knoll mailto:lars.kn...@qt.io>> wrote: On 9 Dec 2020, at 18:49, Thiago Macieira mailto:thiago.macie...@intel.com>> wrote: On Wednesday, 9 December 2020 02:00:29 PST Benjamin TE

Re: [Development] Touchpad gestures on Wayland

On 2 Dec 2020, at 00:38, Povilas Kanapickas mailto:povi...@radix.lt>> wrote: Hello, I would like to implement support for Wayland touchpad gestures[1] to Qt. Would you potentially accept such a contribution from an outside developer if the CLAs are signed and other legal conditions are accepted

Re: [Development] Qt 6 co-installability with Qt 5

> On 9 Nov 2020, at 19:27, Shawn Rutledge wrote: > > >> On 2 Nov 2020, at 17:15, Thiago Macieira wrote: >> ]qml is like Python: because of plugins, it's tied to the Qt version. >> Therefore, it fails the requirement for supporting everything the old >>

Re: [Development] Qt 6 co-installability with Qt 5

> On 2 Nov 2020, at 17:15, Thiago Macieira wrote: > ]qml is like Python: because of plugins, it's tied to the Qt version. > Therefore, it fails the requirement for supporting everything the old version > supported. Well if you were using modules that are no longer supported, or you run into

Re: [Development] Long-lived P1 issues

On 3 Nov 2020, at 12:56, Eike Ziller mailto:eike.zil...@qt.io>> wrote: It is something that we interpret into a combination of two separated fields in JIRA, with the meaning of Fix Version even having dual meaning depending on the “Resolution” state of a task Maybe we should have two fix ver

Re: [Development] Long-lived P1 issues

> On 3 Nov 2020, at 09:07, Ulf Hermann wrote: > >> Currently, there are 1175 open P1 issues in the QTBUG project. 583 of those >> issues had that priority set more than one year ago, 342 of those had their >> priority set more than two years ago, and 175 of those more than three years >> ago

Re: [Development] Proposal: let's use Markdown for the dist/changes changelog

> On 2 Nov 2020, at 20:03, Oswald Buddenhagen wrote: > > On Mon, Nov 02, 2020 at 10:26:31AM +0000, Shawn Rutledge wrote: >> [stuff about changelogs] > > for completeness: > > some of your points re-iterate what has already been said in > https://bugreports.qt.i

Re: [Development] Proposal: let's use Markdown for the dist/changes changelog

On 2 Nov 2020, at 16:59, Thiago Macieira mailto:thiago.macie...@intel.com>> wrote: On Monday, 2 November 2020 02:26:31 PST Shawn Rutledge wrote: So in practice, changelogs still require manual editing. Probably there is someone who knows just what settings to use in just what editor to m

Re: [Development] Qt 6 co-installability with Qt 5

> On 1 Nov 2020, at 01:19, Kevin Kofler via Development > wrote: > > Really, it is this whole concept of the user choosing a version of Qt that > is flawed. The right place to make this choice is the build system of the > software using Qt. Sorry for snipping so much, but it seems like all y

Re: [Development] Qt 6 co-installability with Qt 5

> On 27 Oct 2020, at 20:33, Thiago Macieira wrote: > > On Tuesday, 27 October 2020 10:06:32 PDT Shawn Rutledge wrote: >>> On 27 Oct 2020, at 17:34, Thiago Macieira >>> wrote: > >>> Have we fixed it? >>> >>> I do not plan on

Re: [Development] Qt 6 co-installability with Qt 5

> On 27 Oct 2020, at 17:34, Thiago Macieira wrote: > > Have we fixed it? > > I do not plan on updating qtchooser for Qt 6. Qt 6 should not install any > binary with the same name as Qt 5 did. Well I still use it for Qt 6. It works fine, but I suppose we’ve added some new binaries that need

Re: [Development] QEvent::accept() vs. the newer event delivery algorithms in Qt Quick; remaining API issues; etc.

> On 16 Oct 2020, at 22:43, Giuseppe D'Angelo via Development > wrote: > > Specifically: mouse events have been designed for 90's (?) widgets; they come > with assumptions that clearly show this, like the ones you mentioned: > > * there is only one mouse cursor; > * a mouse event lands first

[Development] QEvent::accept() vs. the newer event delivery algorithms in Qt Quick; remaining API issues; etc.

If you subclass QQuickItem and start handling events, it becomes clear that QEvent::accept() has always meant two things in legacy Qt Quick: 1) stop propagation and 2) grab the mouse. (Does this idea bother you yet?) The item is basically saying “the buck stops here”: it’s so very sure that no

Re: [Development] QProperty and library coding guide

> On 2020 Jul 16, at 11:19, Ulf Hermann wrote: > > Data bindings are a cornerstone of most modern UI frameworks, and Qt is > actually late to the game. If we want Qt to stay relevant, then it needs to > offer the same kind of convenience and performance that other frameworks > offer. This wou

Re: [Development] QtWayland Compositor and marketplace

> On 2020 Jul 6, at 18:57, Pier Luigi Fiorini > wrote: > > Hi, > > I noticed that some modules are going into the marketplace, for example Qt > Multimedia. > Would you consider doing so for QtWayland Compositor? > > The compositor API would surely benefit from a faster release cycle. > > Ge

Re: [Development] Optional network capabilities in QML

> On 2020 Jun 17, at 10:01, Ulf Hermann wrote: > > Hi Carlos, > >> In Qt 5.15.0, I compiled QML without network support successfully, so the >> bug was fixed and so there's no need for the issue. >> On the other hand, you only mention the compilation error, which is not the >> main topic here

Re: [Development] Switch the main "Qt Build System"

> On 2020 Jun 9, at 11:05, Alexandru Croitor wrote: > >> On 9. Jun 2020, at 10:38, Shawn Rutledge wrote: >> >> Well that’s a little extra maintenance work then; I agree that configure is >> nicer, but maybe we can expect the cmake way of configuring to gener

Re: [Development] Switch the main "Qt Build System"

> On 2020 Jun 9, at 10:21, Alexandru Croitor wrote: > >> On 9. Jun 2020, at 09:27, Shawn Rutledge wrote: >> >> FWIW the configuration mechanism seems a bit less friendly so far with all >> those -DSHOUTED options like -DFEATURE_developer_build=ON instead of

[Development] Using clazy to build Qt and Qt-based projects

Since https://codereview.qt-project.org/c/qt/qtbase/+/303079 landed, there are a lot of deprecation warnings. I’ve been using clazy to fix them, as in https://codereview.qt-project.org/c/qt/qtbase/+/303079

Re: [Development] Switch the main "Qt Build System"

FWIW the configuration mechanism seems a bit less friendly so far with all those -DSHOUTED options like -DFEATURE_developer_build=ON instead of configure -developer-build. But there is cmake-gui, which generates checkboxes for all the options after you have run cmake the first time. They are e

Re: [Development] QMetaMethod in Qt 6

> On 2020 May 27, at 17:50, Thiago Macieira wrote: > > On Wednesday, 27 May 2020 03:42:19 PDT Oswald Buddenhagen wrote: >>> this is not something we can subject our users to. >> >> orly? kde had been doing that for quite a while. > > And I fixed QtCore to do the same. > > The only reason not

Re: [Development] QInputEvent refactoring

> On 2020 May 26, at 17:27, Shawn Rutledge wrote: > If it worked with a native swipe gesture instead, maybe it would only > receive the gesture if you are swiping from the screen edge, and only on > certain platforms. But the swipe gesture can be something else on touchpads, c

Re: [Development] QInputEvent refactoring

> On 2020 May 26, at 16:27, Henry Skoglund wrote: > Hi, I tried some QGestureEvents this winter in my first Qt iOS app, and got > bored having to use 3 fingers on my iPhone for swiping (1 finger seems to be > the norm on Android and iPhones). And I discovered that it was pretty easy to > integ

Re: [Development] Nominating Ivan Komissarov as approver

> On 2020 May 7, at 10:23, Christian Kandeler wrote: > > Hello, > > I'd like to nominate Ivan Komissarov as an approver. > Ivan has been doing valuable work in the qbs project for a while now, both as > a contributor and a reviewer. > I trust him to use his approver rights responsibly. > > Hi

Re: [Development] Stepping down as moc maintainer.

> On 2020 May 5, at 09:43, Lars Knoll wrote: > > I’m happy to say that I have a great candidate who’d be willing to take over > the maintainership. Fabian Kosmale would be interested in taking over from > Olivier. He has been working on a couple of features for the moc over the > last month,

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

> On 2020 Apr 23, at 10:27, Simon Hausmann wrote: > > Hi Dmitriy, > > No, this is not an April's Foolk joke. > > Previous discussions were largely centred around the implementations and > bringing them together. With this thread my concern is the API and the churn > our users would have to a

Re: [Development] Finishing the transition to the cherry-pick model

> On 20 Apr 2020, at 07:59, Tuukka Turunen wrote: > > > Hi, > > +1 > > I would also close Qt 5.14 branch already now. > > The other option is that some fixes pushed into Qt 5.14 branch at the time of > Qt 5.15 RC1 only land in Qt 5.15.1. > > Neither of these is problematic to me, assuming

Re: [Development] Github issues

Hmm, maybe we should add README.md to each repo, to direct users to the right places for bugs and patches. ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

Re: [Development] Nominating Daniel Smith as approver

> On 2 Mar 2020, at 17:40, Volker Hilsheimer wrote: > > Hi all, > > > I’d like to nominate Daniel Smith as approver for the Qt Project. +1 he’s been doing a great job on several fronts ___ Development mailing list Development@qt-project.org https:

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

On 28 Feb 2020, at 21:33, Lars Knoll mailto:lars.kn...@qt.io>> wrote: So to shortcut this discussion a bit: I am completely opposed to a massive SIC changes/efforts for our signals (like giving them ugly names like emitClicked(), or signal objects). If people feel strongly, I am open to tryi

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

> On 24 Feb 2020, at 10:54, Ville Voutilainen > wrote: > > On Mon, 24 Feb 2020 at 11:23, Jean-Michaël Celerier > wrote: >> >> A good inspiration for that feature would be the Just My Code feature of >> recent visual studio : >> https://docs.microsoft.com/en-us/visualstudio/debugger/just-my-

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

> On 22 Feb 2020, at 12:57, Ville Voutilainen > wrote: > > On Sat, 22 Feb 2020 at 13:07, André Pönitz wrote: >>> Buy a debugger that can skip code that you didn't write. >> >> The point was that in a such a situation I, as user, would not even >> try to step in when the call is marked with 'e

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

> On 21 Feb 2020, at 14:26, Giuseppe D'Angelo via Development > wrote: > > Il 21/02/20 13:59, Shawn Rutledge ha scritto: >> (Some people name every slot function starting with the word “slot” to make >> clear what it is.) > > So, literally any function th

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by 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 it's a signal. Not all signals follow the > *Changed() naming co

Re: [Development] Co-maintainer of QtNetwork

+1 On 20 Feb 2020, at 06:48, Timur Pocheptsov mailto:timur.pochept...@qt.io>> wrote: Hi all, I want to propose a colleague of mine, Mårten Nordheim, as a co-maintainer of QtNetwork module with him becoming the maintainer of „High-Level network access (HTTP)"* (which essentially means QNetwor

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

> On 5 Feb 2020, at 16:31, Edward Welbourne wrote: > > Shawn Rutledge (5 February 2020 14:14) >> So I’m strongly in favor of continuing to do deprecations as long as >> possible. A deprecation is not something that can break existing >> functionality, so it’s no

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

On 5 Feb 2020, at 13:04, Jani Heikkinen mailto:jani.heikki...@qt.io>> wrote: We are doing time based releases so if new feature misses the deadline there will be next one coming after few months. It might be quite long time for unique feature but on the other hand it isn't really that long… I

[Development] Models for QML (was Re: The future of smart pointers in Qt API)

> On 3 Feb 2020, at 10:26, Ola Røer Thorsen wrote: > > - The biggest struggle I have with Qt currently regarding pointers is when > you share a dynamic model of QObject* to qml. Here it would actually be > useful to have shared_ptr, and I've solved this with some Q_GADGET-based > wrappers. (O

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

> On 3 Feb 2020, at 17:59, Jason H wrote: > > Recently this has caused me much consternation. I think QtQuick everything > should have a parent, and a visual parent, though I appreciate how tedious > this would be. They should be the same except when they can't and having > separate propertie

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

On 1 Feb 2020, at 19:20, Daniel Teske mailto:q...@squorn.de>> wrote: Now to take your next example: setParent is not fine. setParent can be used in 4 different ways: child->setParent(child->parent()): Invariant holds child->setParent(newParent): Invariant holds child->setParent(nullptr): Nope

  1   2   3   4   >