summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGravatar Dirk Hohndel <dirk@hohndel.org>2016-04-02 11:04:44 -0500
committerGravatar Dirk Hohndel <dirk@hohndel.org>2016-04-02 12:47:00 -0500
commit09856b4546de1fd2de563e51a4f26b42eedfeaef (patch)
tree346a44e0d482a0e8613f481ba597b6fa328aa8f0
parent254ea5accb25cf3218af8df7da6471d10bceee5b (diff)
downloadsubsurface-09856b4546de1fd2de563e51a4f26b42eedfeaef.tar.gz
QML UI: work around problem starting some actions while on the App log
If you show the App log and then start "Add dive manually" or "Show GPS fixes" you get this odd behavior that the page stack returns to the App log for some reason. A simple workaround is of course to return to the dive list, first. Not ideal (because there shouldn't be a reason not to have the All log in the stack as well, but not really a big problem, either, since the App log is mainly intended for developers. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
-rw-r--r--qt-mobile/qml/main.qml2
1 files changed, 2 insertions, 0 deletions
diff --git a/qt-mobile/qml/main.qml b/qt-mobile/qml/main.qml
index b578ffe51..c011ba4c1 100644
--- a/qt-mobile/qml/main.qml
+++ b/qt-mobile/qml/main.qml
@@ -126,6 +126,7 @@ Kirigami.ApplicationWindow {
Kirigami.Action {
text: "Add dive manually"
onTriggered: {
+ returnTopPage() // otherwise odd things happen with the page stack
startAddDive()
}
}
@@ -174,6 +175,7 @@ Kirigami.ApplicationWindow {
Kirigami.Action {
text: "Show GPS fixes"
onTriggered: {
+ returnTopPage()
manager.populateGpsData();
stackView.push(gpsWindow)
}