| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
According to https://wiki.qt.io/Writing_Qt_Examples
Task-number: QTBUG-60649
Change-Id: I17073bb3caf32ccd17d93542876a73ed939f12bd
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
|
|
|
|
|
|
|
| |
See also https://wiki.qt.io/Writing_Qt_Examples
Task-number: QTBUG-60649
Change-Id: I3a5671f39e870f96546e66427cc9434f41777e33
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
|
|
|
|
| |
Change-Id: Id8cc29a9a27f571f063b1cec51e534a3c762f2c6
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
Adding QObjects as context properties to QML engines is not the best
way to interoperate between QML and C++. This change exposes all state
machines as proper QML components and instantiates them from QML. Also,
it drops all the now unnecessary init() calls.
Change-Id: Id44b4038542dd9469e02831c1bb54f096af1b6ff
Reviewed-by: Erik Verbruggen <erik.verbruggen@theqtcompany.com>
|
|
The release process puts all examples based on their module name into
the same directory. Therefore each module has to group its examples
based on their module name.
Change-Id: I3695297ff0489fbbb2c4f4aa13e0c4baa7f011b7
Reviewed-by: Jarek Kobus <jaroslaw.kobus@theqtcompany.com>
|