caspervk/AndroidAPS
1
0
Fork 0
Code Releases Activity

Wait up to 90s before timing out on connection attempt.

Browse source 
Might take longer if we need to wait for the pump display to time
out due to recent user activity.
This commit is contained in:
Johannes Mockenhaupt 2017-07-20 18:28:39 +02:00
parent a28efb4be0
commit cb8a22582a
No known key found for this signature in database
GPG key ID: 9E1EA6AF7BBBB0D1
1 changed files with 10 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
app/src/main/java/de/jotomo/ruffyscripter/RuffyScripter.java
View file

@ -294,8 +294,11 @@ public class RuffyScripter {
log.debug("Connect init successful: " + connectInitSuccessful);
while (currentMenu == null) {
log.debug("Waiting for first menu update to be sent");
// waitForMenuUpdate times out after 60s and throws a CommandException
waitForMenuUpdate();
// waitForMenuUpdate times out after 60s and throws a CommandException.
// if the user just pressed a button on the combo, the screen needs to time first
// before a connection is possible. In that case, it takes 45s before the
// connection comes up.
waitForMenuUpdate(90);
}
} catch (RemoteException e) {
throw new CommandException().exception(e).message("Unexpected exception while initiating/restoring pump connection");
@ -343,7 +346,11 @@ public class RuffyScripter {
* Wait until the menu update is in
*/
public void waitForMenuUpdate() {
long timeoutExpired = System.currentTimeMillis() + 60 * 1000;
waitForMenuUpdate(60);
}
public void waitForMenuUpdate(long timeoutInSeconds) {
long timeoutExpired = System.currentTimeMillis() + timeoutInSeconds * 1000;
long initialUpdateTime = menuLastUpdated;
while (initialUpdateTime == menuLastUpdated) {
if (System.currentTimeMillis() > timeoutExpired) {