| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
Change-Id: I2963549e118f2166ce8a23c63e62b54cba1b644b
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
| |
The code was already written to have a dummy API implementation,
if QtDBus is not available.
Change-Id: I93a701aad32ce80b9bd07c2aad463481d4e7fe98
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
|
|
|
|
|
|
|
| |
Also put more emphasis on the scaling issue.
This was decided in the 6.5 CMake API review.
Change-Id: I4ad8d39434bb514513a4864ec7081a264d928d42
Reviewed-by: Bernd Weimer <bernd.weimer@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The header stopped being generated by syncqt/cpp on certain
platforms because we only generate headers that meet
the qt_internal_extend_target conditions. In this case qtwayland is
not available on macOS, and thus the waylandwindow.h header is not
generated.
Fix windowframetimer.cpp to include it conditionally only if the
multi process feature is enabled.
Not generating the header is fine in this case, because the whole
module is Private, even though the header has no _p.h suffix.
This unblocks the build with syncqt/cpp.
Fixes: QTBUG-109337
Change-Id: I0a38af6d23e5d1c9e040281a52a3b719106382b9
Reviewed-by: Zoltan Gera <zoltan.gera@qt.io>
Reviewed-by: Robert Griebl <robert.griebl@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
| |
This fixes errors for the developer-build.
Task-number: QTBUG-109337
Change-Id: I145e5eb5074f6e8b03e3304f58f0dd57ee1dfe95
Reviewed-by: Zoltan Gera <zoltan.gera@qt.io>
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Reviewed-by: Robert Griebl <robert.griebl@qt.io>
|
|
|
|
|
|
|
|
|
| |
Add interface dependencies to fix top-level builds. Add
PRIVATE_HEADER_FILTERS for the generated wayland code.
Task-number: QTBUG-87480
Change-Id: I6f35777786bf4356cd8cd2c31709601a08407912
Reviewed-by: Robert Griebl <robert.griebl@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
Tag tells coin that the module expects to build documentation.
Coin then adds the qt5 doc workitem to the integration which ensures
that the top level docs are in place when the module needs them.
Change-Id: I41d51a5e3ce93c86e5b351e3f320ed382b9a4606
Reviewed-by: Toni Saario <toni.saario@qt.io>
(cherry picked from commit e5b58b1d7fbd10f6b94e1a421e385e423fcc6abf)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Key events were not passed to applications, when the focus moved to
a WindowItem in the System UI, since the item representing the
application window is actually a child of the WindowItem.
A possible solution would be to explicitly send the key events to the
application item, though the approach taken here is to forward the
keyboard focus. This results in key events always reaching the
application first (even when the System UI would actually consume the
events) and in single-process mode, if the application consumes the
event the System UI won't get it any more.
Fixes: QTBUG-108837
Change-Id: I1699556f1a67057e8be2848e37c846c2ee33a646
Reviewed-by: Robert Griebl <robert.griebl@qt.io>
|
|
|
|
|
| |
Change-Id: I62dfd8b138ba95b74fa0cd8dab83363977c03201
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I86e6daea6ed7201d44720ceee5218be49297818b
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I647ad7724e6a89b1522d2d81cf8e7e67c8a6f5e0
Reviewed-by: Robert Griebl <robert.griebl@qt.io>
|
|
|
|
|
| |
Change-Id: I164daebaccf3159a18e9e494ab6facd15ba2d656
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I9c5371a631517e1b7c1225af3e9410280525fa51
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I3813c10ab8f5288fc90c23f72412efe2fcc8005a
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I86248c136880947a8d6554dd48e2602c470715a1
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I2e8b3f4ac94c1edb1ae637c0fc0bfd3c6472957b
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I56b9bdf7f01cc157e2165673fccaadb9c6a61a57
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Iefa98c469426371a3e4cad9f2be8ef7b9bbb96c0
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Id8f6aebe5a6b23433b11ee35aad29243a5ffafbc
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
| |
After qtbase commit 8539e641f6f48a605547f66c47266d19e537f74e,
opengl headers are not available if the feature is disabled.
Change-Id: Ib5f30f67b83a07f98053c8afdea4125d215558b6
Reviewed-by: Robert Griebl <robert.griebl@qt.io>
|
|
|
|
|
| |
Change-Id: I28834fe941d8578f576ebb4ff0fa91d27a50b634
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If you were calling startApplication() and the runtime failed to
execute the app's binary in a container, it would call deleteLater() on
the failed runtime object. The problem was that if you immediately
called startApplication() once more in the same event loop iteration,
the Application object still had the to-be-deleted runtime attached,
which in turn prevents the allocation of a new container, so the
AM tried to start the application again, but this time with
"container" set to nullptr.
The actual fix is to NOT call deleteLater, but directly delete the
runtime object.
In addition, when startApplication() is called for an application,
we have to make sure that the application's runtime object can not
be in the state NotRunning: the AM could still end up in this state,
if a Container plugin is either not reporting shutdown correctly, or
if the container's "ready" state is delayed.
Change-Id: Ied1baec8c90d4e0a980c296cbc7cd87b12629524
Pick-to: 6.4 6.3 6.2 5.15
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
|
|
|
|
|
| |
Change-Id: I0f7610564534ff66232fdbe810d8cce8e1c30822
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
| |
Change-Id: I29142dccb62f4f9689a13f0dd5d9b1d4f9f81e05
Pick-to: 6.4 6.3 6.2 5.15
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
|
|
|
|
|
|
| |
Change-Id: If89030ffc9736b850f0dc2e57b84fcbe106f5921
Pick-to: 6.4
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
|
|
|
|
|
| |
Change-Id: I3fdbaea392fe96643d99df46a846118d7c711623
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: I1b668c3c26c416d253fb33118a1d9f588e8494db
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ibf2ac10ab020000924d42750c417ff7eb889774e
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
| |
Change-Id: I33b43f1af4f052ef70fdad80b6abf8cec91f5930
Pick-to: 6.4 6.3 6.2
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
|
|
|
|
|
|
| |
Fixes: AUTOSUITE-1673
Change-Id: I95bb5768aa96f35a9941ea29492d52eb789d4075
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
|
|
|
|
|
|
|
|
| |
In case the qtauto-deployment-server repo will be updated in the
future, this tool will move to that repo.
Change-Id: I93109a8f08bfd6cab6d96242115099eba48231b6
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
|
|
|
|
|
| |
Change-Id: Iac6f64568d8e5fb6e508f4a0848bc3755f826609
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The tool syntax got ported over from the old qmake system, but this
leads to problems nowadays on cross or multi-config builds, where the
tools are not built at all, unless they are built explicitly.
What we call tools, really are apps for Qt's cmake build system, so
all of those (except the packager and uploader (*), which really are build-
time tools) have been converted to be built as apps.
(*) the uploader should be retired or moved to the
qt-apps/qtauto-deployment-server repository anyway.
Change-Id: I7be0ce63625e53d0bc65387c5e5200c71c00b48a
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
|
|
|
|
|
| |
Change-Id: I33b6c0efa6f20ffc57d1ddf57fb34ccb4154765e
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
| |
Change-Id: I1e31754344e4880cb493b5f118e98be2ae725960
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
|
|
|
|
|
|
|
|
| |
This makes testing and debugging Intents a lot easier, especially
since you can even fake the requesting application id.
Change-Id: Ie5d46bd2e3a9962ca533bf75d7262c20f95d42b6
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit adds a new intent type: a broadcast.
Broadcasts will be delivered to all applications (*), but they do not have
the possibility to return a reply back to the sender.
Implementation wise, they are just treated as normal requests that are
multiplexed for every application.
(*) This can be limited with the new handleOnlyWhenRunning flag.
Change-Id: If9f954cf5e52707624b95c80c8e984dfd6c4315a
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
|
|
|
|
|
|
| |
Change-Id: Ibfbfa43ea68fac81ae001197e67d8fe9596ab277
Pick-to: 6.4
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
|
|
|
|
|
| |
Change-Id: I4934f79e8d9661e6c82f8e54c37eb1e6821eb70c
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Ic4c9f826b48531c82d3eaf40936f036b8591db3d
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
| |
Don't call QTestRootObject::init() before starting the test.
This causes all variables to be reset, including hasTestCase and
causes the event loop not to be started.
Pick-to: 6.2 6.3 6.4
Fixes: QTBUG-106088
Change-Id: Idaa114efaed1a306aca3affd6f255d918f1a6d29
Reviewed-by: Bernd Weimer <bernd.weimer@qt.io>
|
|
|
|
|
| |
Change-Id: Icb05f53521b26b15c14d93b0b1f780ad3f33c681
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
| |
This was not a big problem until now, as only the installer itself was
using this flag.
Change-Id: I1b7a749c5066aa13959dd4d798bd545c3070bac7
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
|
|
|
|
|
| |
Change-Id: I127e20a94b01854d8803290a1de88299ecb03582
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
std::remove_if() on a QMap should result in a compile-time error, but
it somehow doesn't. Instead the erase(remove_if()) algorithm leaves
a corrupted QMap.
This is especially noticeable in single-process mode, where the wrong
intent handlers are being called after closing any single application,
which registered IntentHandlers before.
This bug was introduced while fixing clazy warnings.
Change-Id: I144c051591ce8564e2653402d12bb926ef32eb76
Pick-to: 6.4 6.3 6.2
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
|
|
|
|
|
| |
Change-Id: I1998306a466371490f5ac1c88d4719250e2b2842
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
| |
This fixes compilation errors even for older versions of glibc.
Change-Id: I930010d20cff1dac7340c5897e39a929b3054cbd
Fixes: QTBUG-105688
Pick-to: 6.4
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
|
|
|
|
|
|
| |
Change-Id: I4d6bf4d4d29133202c0b7dfd088d09cf2a64d1c0
Pick-to: 5.15 6.4
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
|
|
|
|
|
|
| |
Change-Id: Ia71cf0b596b4e90d38fba0ca5d1c6134e96e721f
Pick-to: 5.15 6.4
Reviewed-by: Robert Griebl <robert.griebl@qt.io>
|
|
|
|
|
|
| |
Change-Id: Ib4e94bebdd2b2416a9ed6a5fc21e357223ab36fb
Pick-to: 6.2 6.3 6.4
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
|