| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
Instead, make the data model a Q_PROPERTY of state machines. This makes
it much easier to independently instantiate state machines and data
models from QML and connect them via properties.
Change-Id: I62d712dd0ad7817c39432204ced431b8041e442d
Reviewed-by: Erik Verbruggen <erik.verbruggen@theqtcompany.com>
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
|
| |
We will have one data model per state machine, so the overhead of
creating a QObject won't be significant. However, we can expose the
data model to QML this way. Also, by using QObjectPrivate, we can
actually drop a few d-pointers.
Change-Id: I8a73dde017e8fd38032f4948e2946590456b4cc9
Reviewed-by: Erik Verbruggen <erik.verbruggen@theqtcompany.com>
|
| |
|
|
|
|
| |
Change-Id: Id38eb2b75e5205b74238151b20a279ba71442713
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@theqtcompany.com>
Reviewed-by: Alex Blasche <alexander.blasche@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>
|
