subsurface/qt-mobile
Dirk Hohndel c0ac953242 QML UI: call plot dive when we set the dive
The asynchronous nature of the profile bites us here. plotDive() signals
that it changes model data and expects the rest of the data structures to
respond to that. Very neat and it seems to work perfectly well on the
desktop, but on Android calling render() right after plotDive() resulted
in paint() functions being called before all the elements had been
calculated as a result of the signals being emitted in the model change.
That's why so often the profile was missing parts.

Now admittedly this makes me nervous. Do we now know that all calculations
have finished by the time render() gets called? Not really. It just seems
that in my testing we tend to get lucky and things work out. But that does
not feel like a sane architecture to me.

Messing around with the animation speed is silly as we render the profile
into a pixmap, so let's turn this off globally.

Also, the scaling of the pixmap is still completely bogus.

Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2015-12-01 15:32:16 -08:00
..
qml QML UI: don't load dives before the UI has been instantiated 2015-11-30 10:15:04 -08:00
qmlmanager.cpp QML-UI: make sure errors make it to the log 2015-12-01 09:37:47 -08:00
qmlmanager.h Location service: move into subsurface-core 2015-11-18 18:34:49 -08:00
qmlprofile.cpp QML UI: call plot dive when we set the dive 2015-12-01 15:32:16 -08:00
qmlprofile.h Cache diveprofile widget in the diveprofile QtQuick item 2015-11-11 19:06:00 -08:00