From c0ac9532427dee713c8ba96a1ceb10ee78b2bfc8 Mon Sep 17 00:00:00 2001 From: Dirk Hohndel Date: Tue, 1 Dec 2015 15:22:38 -0800 Subject: 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 --- subsurface-mobile-main.cpp | 1 + 1 file changed, 1 insertion(+) (limited to 'subsurface-mobile-main.cpp') diff --git a/subsurface-mobile-main.cpp b/subsurface-mobile-main.cpp index 079dbcc0a..279255ace 100644 --- a/subsurface-mobile-main.cpp +++ b/subsurface-mobile-main.cpp @@ -58,6 +58,7 @@ int main(int argc, char **argv) taglist_init_global(); init_ui(); loadPreferences(); + prefs.animation_speed = 0; init_proxy(); if (no_filenames) { if (prefs.default_file_behavior == LOCAL_DEFAULT_FILE) { -- cgit v1.2.3-70-g09d2