qt/qtdeclarative.git/src/quicktemplates/qquickpresshandler_p_p.h, branch dev Qt Declarative (Quick 2) Set explicit default security level of all files with default security 2025-09-17T13:31:14+00:00 Jan Arve Sæther jan-arve.saether@qt.io 2025-09-16T13:35:55+00:00 01cd43d30e3ca2c4dd94a4a4711604adb9417517 The files (folders) already processed are listed in each issue in epic QTBUG-134547 These files were processed half a year ago. In order to make it clear that all of these files are already processed, mark them with an explicit default security header. For the record, this was generated with this script: find -E . -regex ".*\.(cpp|h|hpp|mm|qml|js)$" | xargs python3 ~/bin/add-cra-header.py in the folders listed in each subtask of QTBUG-134547 (add-cra-header.py only exist at my desktop, but it simply adds the default security header if it doesn't already have any existing security header) QUIP: 23 Fixes: QTBUG-134547 Pick-to: 6.10 6.9 6.8 Change-Id: Ieb8c78ea6561fdbdd27c7b13185ece853eedf80f Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io> 
The files (folders) already processed are listed in each issue in epic
QTBUG-134547

These files were processed half a year ago. In order to make it clear
that all of these files are already processed, mark them with an
explicit default security header.

For the record, this was generated with this script:

find -E . -regex ".*\.(cpp|h|hpp|mm|qml|js)$" | xargs python3 ~/bin/add-cra-header.py

in the folders listed in each subtask of QTBUG-134547

(add-cra-header.py only exist at my desktop, but it simply adds the
default security header if it doesn't already have any existing security
header)

QUIP: 23
Fixes: QTBUG-134547
Pick-to: 6.10 6.9 6.8
Change-Id: Ieb8c78ea6561fdbdd27c7b13185ece853eedf80f
Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
QQuickPressHandler: c++23 compile fix 2025-08-05T00:47:29+00:00 Tim Blechmann tim.blechmann@qt.io 2025-08-04T04:27:07+00:00 3bf35c1d9e9b11a93236612cd4b93e8a7b6519f1 When building with c++23, the `= nullptr` assignment to a unique_ptr fully instantiates the underlying type to synthesize the destructor. This means the forward declaration cannot be used. Relying on the default constructor as workaround. Pick-to: 6.8 6.9 6.10 Change-Id: Iff411ae5ea6fe716dc1e2c2c4dbba9e46918fae5 Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> 
When building with c++23, the `= nullptr` assignment to a unique_ptr
fully instantiates the underlying type to synthesize the destructor.
This means the forward declaration cannot be used.

Relying on the default constructor as workaround.

Pick-to: 6.8 6.9 6.10
Change-Id: Iff411ae5ea6fe716dc1e2c2c4dbba9e46918fae5
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
quicktemplates: include missing headers 2023-04-14T11:20:42+00:00 Tim Blechmann tim@klingt.org 2023-04-14T03:29:10+00:00 8fc8a2df6ed404ff19fb59a655e669c78318bcfe compile fix with clang++/libstdc++: unique_ptr requires <memory> Pick-to: 6.5 Change-Id: Ib01f660b6b43ee1eb5d729fbbd7b064cdfd22e9b Reviewed-by: Mitch Curtis <mitch.curtis@qt.io> 
compile fix with clang++/libstdc++: unique_ptr requires <memory>

Pick-to: 6.5
Change-Id: Ib01f660b6b43ee1eb5d729fbbd7b064cdfd22e9b
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
QQuickPressHandler: Fix delayedMousePressEvent leak 2023-02-17T07:02:12+00:00 Fabian Kosmale fabian.kosmale@qt.io 2023-02-16T14:41:27+00:00 d4bb93cb0580d5dce013e7bcbe2727a98d1ab8bd If the handler is destroyed before something dealt with the delayed event, we would have leaked the events memory so far. Pick-to: 6.5 Change-Id: I3c482621a61e5d9ff8ec101197d140a069c83300 Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io> 
If the handler is destroyed before something dealt with the delayed
event, we would have leaked the events memory so far.

Pick-to: 6.5
Change-Id: I3c482621a61e5d9ff8ec101197d140a069c83300
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
Remove "2" from Qt Quick Controls directories 2022-12-01T02:26:20+00:00 Mitch Curtis mitch.curtis@qt.io 2022-11-18T07:15:16+00:00 4bd87b903b355b53e3105ba1ae7c154c4e55cdaf Qt Quick Controls 2 was named that way because it was a follow-up to Qt Quick Controls 1.x. Now that Qt Quick Controls 1 is no longer supported, we don't need to have "2" in the name. Work on this was already started for the documentation in 1abdfe5d5a052f2298b7bf657513dfa7e0c66a56. By doing this renaming a few weeks before feature freeze, it won't affect the release but still results in as little time possible spent manually fixing conflicts in cherry-picks from non-LTS releases as a result of the renaming. This patch does the following: - Renames directories. - Adapts CMakeLists.txt and other files to account for the new paths. A follow-up patch will handle documentation. It does not touch library names or other user-facing stuff, as that will have to be done in Qt 7. Task-number: QTBUG-95413 Change-Id: I170d8db19033ee71e495ff0c5c1a517a41ed7634 Reviewed-by: Mitch Curtis <mitch.curtis@qt.io> 
Qt Quick Controls 2 was named that way because it was a follow-up to
Qt Quick Controls 1.x. Now that Qt Quick Controls 1 is no longer
supported, we don't need to have "2" in the name. Work on this was
already started for the documentation in
1abdfe5d5a052f2298b7bf657513dfa7e0c66a56.

By doing this renaming a few weeks before feature freeze, it won't
affect the release but still results in as little time possible spent
manually fixing conflicts in cherry-picks from non-LTS releases as a
result of the renaming.

This patch does the following:

- Renames directories.
- Adapts CMakeLists.txt and other files to account for the new paths.

A follow-up patch will handle documentation.

It does not touch library names or other user-facing stuff, as that
will have to be done in Qt 7.

Task-number: QTBUG-95413
Change-Id: I170d8db19033ee71e495ff0c5c1a517a41ed7634
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>