<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="">I just merged yet another set of changes, their main purpose is to get us closer to being able to show the statistics in the mobile app.</div><div class=""><br class=""></div><div class="">There are a few caveats (and because of a couple of them, I'm not QUITE ready to make new iOS and Android test builds available just yet):</div><div class=""><br class=""></div><div class="">This changes the way the statistics get rendered. In order for them to be usable in the QML UI, we need to do something that is pretty atrocious. To quote from the commit message:</div><div class=""><br class=""></div><div class=""><pre style="box-sizing: border-box; font-family: SFMono-Regular, Consolas, "Liberation Mono", Menlo, monospace; font-size: 13px; margin-top: 10px; margin-bottom: 0px; max-width: 100%; line-height: 1.45; color: var(--color-auto-gray-7); white-space: pre-wrap; overflow: visible; overflow-wrap: break-word; font-variant-ligatures: normal; orphans: 2; widows: 2; background-color: rgb(241, 248, 255); text-decoration-thickness: initial;" class="">It turns out that the wrong base class was used for the chart.
QQuickWidget can only be used on desktop, not in a mobile UI.
Therefore, turn this into a QQuickItem and move the container
QQuickWidget into desktop-only code.
Currently, this code is insane: The chart is rendered onto a
QGraphicsScene (as it was before), which is then rendered into
a QImage, which is transformed into a QSGTexture, which is then
projected onto the device. This is performed on every mouse
move event, since these events in general change the position
of the info-box.
The plan is to slowly convert elements such as the info-box into
QQuickItems. Browsing the QtQuick documentation, this will
not be much fun.
</pre></div><div class=""><br class=""></div><div class="">So in certain situations this can lead to 100% CPU consumption - Berthold has seen this situation, I have not in my testing.</div><div class="">This definitely causes a lot of wasted CPU cycles in the desktop version and means there's the chance for visual artifacts (and if you see those, please report with screenshot), but in my testing it seemed to behave basically the same as the old version.</div><div class="">And excitingly, this gives us statistics on mobile (here a screenshot from mobile-on-desktop, but with the screen resolution of my phone simulated)</div><div class=""><br class=""></div><div class=""><img apple-inline="yes" id="8DDC78C9-0F9A-4F1D-91F7-1CAF5399855B" width="323" height="640" src="cid:DCD98E62-CFF6-45C8-81A1-21DED2B040FC" class=""></div><div class=""><br class=""></div><div class=""><img apple-inline="yes" id="2DF9D2DE-E0E9-416E-98BE-F04DFA17E1C4" width="640" height="326" src="cid:296130B7-3D14-4490-BFF2-21D8B5BDADA1" class=""></div><div class=""><br class=""></div><div class="">There are quite a few issues that still need to be addressed (including selection of charts), but it's already surprisingly usable.</div><div class=""><br class=""></div><div class="">This got merged now in order to make sure we don't have diverging code basis and to increase the testing of the code that will eventually be in the next release (instead of testing the older code that would never work for mobile).</div><div class=""><br class=""></div><div class="">There is a LOT of good stuff happening right now, I think.</div><div class=""><br class=""></div><div class="">Also in the pipeline is the addition of calculated deco ceilings on mobile - something quite a few people have been asking about.</div><div class=""><br class=""></div><div class="">/D</div></body></html>