Never block when building a cache/waypoint details creator

Blocking on the UI thread may prevent other looper threads from
executing, including the ones in charge of receiving the location
updates. This may lead to deadlocks when, for example, starting cgeo
from a cache URL if cgeo has not been started before.

1 files changed, 7 insertions, 0 deletions

diff --git a/main/src/cgeo/geocaching/CgeoApplication.java b/main/src/cgeo/geocaching/CgeoApplication.java
index 863dcdd..6eb1235 100644
--- a/main/src/cgeo/geocaching/CgeoApplication.java
+++ b/main/src/cgeo/geocaching/CgeoApplication.java
@@ -108,6 +108,13 @@ public class CgeoApplication extends Application {
         return currentGeo != null ? currentGeo : geoDataObservable().toBlocking().first();
     }
 
+    public Float distanceNonBlocking(final ICoordinates target) {
+        if (currentGeo == null || target.getCoords() == null) {
+            return null;
+        }
+        return currentGeo.getCoords().distanceTo(target);
+    }
+
     public float currentDirection() {
         return currentDirection;
     }