| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Change-Id: I17484583ca02f98d6120816611ccc7e8b0ce43e3
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Just the number of frames per second doesn't tell us the reason for any
low frame rates. The problem could either be GPU-bound, and rendering
could take very long, or the problem could be CPU-bound, with
synchronizing or the gap between frames being very long.
Reporting the rendering and synchronization times in more detail gives
the client an idea of what is actually going on.
Change-Id: Ib2840a9e1aa9b9738e967730c668769946659be2
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
See commit e6f6c4aee6951a for the matching change
in QQmlApplicationEngine.
Also needed to adapt the autotests, since qt_QT is
not (yet) a valid locale.
Task-number: QTBUG-69196
Change-Id: If92156abbb3e20042a934b8150a8f456d8f770b6
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
|
| |
|
|
|
| |
Change-Id: I9afc5a0e1c7807f19dfcca1270267bbf7f718903
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
|
| |
|
|
|
|
|
|
| |
It is instructive to the client to know how many frames per second the
current QML can achieve in the preview.
Change-Id: I8b73e2b5218410d903a07dfe27c038663c84fdee
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
This allows the client to skip the initial "Load" command if the first
.qml file loaded is the source for the root component. Furthermore, it
can just pass an empty URL to Load in order to have the service reload
the last loaded URL.
Change-Id: Iae5b9bdd20dbc8a772f46d97f91adf7092df1ef3
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
|
|
|
Task-number: QDS-181
Change-Id: I02193afb84aa111792d8bebff3bdd9b410f9db5a
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
|
