diff options
| author |  Dirk Hohndel <dirk@hohndel.org> | 2021-08-15 19:53:07 -0700 |
|---|---|---|
| committer | Dirk Hohndel <dirk@hohndel.org> | 2021-08-18 19:09:59 -0700 |
| commit | 454207cd80f1159e9596c236893eba786ff3b918 (patch) | |
| tree | 21a8c41f4f2f81b5fee50953d4f2e2cac1e0248a | |
| parent | 3faff0b7f07349997f7743f3053767797ed3b2b7 (diff) | |
| download | subsurface-454207cd80f1159e9596c236893eba786ff3b918.tar.gz | |
mobile: make cloud timeouts more consistent
In the mobile version we should always allow a little more wait time for
the cloud server - there just seem to be more issues with response times
on mobile devices, especially when in places with poor data reception
(which isn't uncommon for dive sites).
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
| -rw-r--r-- | mobile-widgets/qmlmanager.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/mobile-widgets/qmlmanager.cpp b/mobile-widgets/qmlmanager.cpp index d3ea320c2..e70b18027 100644 --- a/mobile-widgets/qmlmanager.cpp +++ b/mobile-widgets/qmlmanager.cpp @@ -692,7 +692,7 @@ bool QMLManager::verifyCredentials(QString email, QString password, QString pin) QEventLoop loop; connect(csa, &CloudStorageAuthenticate::finishedAuthenticate, &loop, &QEventLoop::quit); connect(&myTimer, &QTimer::timeout, &loop, &QEventLoop::quit); - myTimer.start(5000); + myTimer.start(prefs.cloud_timeout * 1000); loop.exec(); if (!myTimer.isActive()) { // got no response from the server |