| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Change-Id: I82424fe66172851f3652ca6acbb4f4d6694a71c2
Reviewed-by: Robert Griebl <robert.griebl@qt.io>
(cherry picked from commit c6448d7661eb165fa9284d67161faf4918f7bc60)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
| |
Also removed all the SPDX tags and -QTAS license extensions.
Change-Id: Ibd10fe37afcbba832831d027cf2f1891ca0226c0
Fixes: AUTOSUITE-1648
Fixes: AUTOSUITE-1646
Reviewed-by: Dominik Holland <dominik.holland@qt.io>
|
|
|
|
|
|
|
|
|
| |
Don't use implicitly defined handler, since this is deprecated from
Qt 5.15. This works since Qt 5.14 only, but we are tied to 5.15,
anyways.
Change-Id: I82e66b0c6186237757e060bfb21d86c91ec8498b
Reviewed-by: Robert Griebl <robert.griebl@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Those classes are not restricted to QML, but provide general inter-
process communication via DBus. They can be used from native
applications, as well:
- QmlApplicationInterface to DBusApplicationInterface
- QmlApplicationInterfaceExtension to DBusApplicationInterfaceExtension
- QmlNotification to DBusNotification
Task-number: AUTOSUITE-1260
Change-Id: Iaff6251e61d62b7173e0e17a81863b4f653e8b5d
Reviewed-by: Robert Griebl <robert.griebl@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
This allows native applications to use LauncherMain and still choose
the application typ, e.g. QApplication for a native widget
application.
Task-number: AUTOSUITE-1260
Change-Id: Id5f643ebc1a9e413ed6f9b8cf8b3259fa0448859
Reviewed-by: Robert Griebl <robert.griebl@qt.io>
|
|
|
|
|
|
|
|
| |
- Also add in the exampleurl qdocconf file to improve navigability
Task-number: AUTOSUITE-1142
Change-Id: Ie7fd72b9eeeebc9dab15360c22343a10fa5bb018
Reviewed-by: Bernd Weimer <bernd.weimer@pelagicore.com>
|
|
This example showcases client applications with various features,
including a native application.
Change-Id: Id7a8a40481b8b9503434f6576f3bf9f97b093435
Task-number: AUTOSUITE-1142
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|