| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Qml Preview: Record more detailed frame statistics | Ulf Hermann | 2018-09-10 | 1 | -1/+13 |
| | | | | | | | | | | | | | | 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> | ||||
| * | Tooling: Allow QML preview to change the language | Ulf Hermann | 2018-07-20 | 1 | -1/+3 |
| | | | | | | Change-Id: I9afc5a0e1c7807f19dfcca1270267bbf7f718903 Reviewed-by: Simon Hausmann <simon.hausmann@qt.io> | ||||
| * | QML Preview: Add a frames per second counter | Ulf Hermann | 2018-07-18 | 1 | -1/+3 |
| | | | | | | | | | 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> | ||||
| * | Tooling: Add QML preview debug service | Ulf Hermann | 2018-07-13 | 1 | -0/+95 |
| Task-number: QDS-181 Change-Id: I02193afb84aa111792d8bebff3bdd9b410f9db5a Reviewed-by: Simon Hausmann <simon.hausmann@qt.io> | |||||
 |
index : qt/qtdeclarative.git | |
| Qt Declarative (Quick 2) |
| aboutsummaryrefslogtreecommitdiffstats |