Simplify comparison implementation

This was triggered by issue #3532. The comparator interface could return
the following facts simultaneously A == B, A == C, B < C if A could
not be compared to others.

Now we will have A placed after B and C in any case.

Also, since most comparators can compare all caches, the defalut is true
and can be overriden if needed.

1 files changed, 0 insertions, 5 deletions

diff --git a/main/src/cgeo/geocaching/sorting/PopularityRatioComparator.java b/main/src/cgeo/geocaching/sorting/PopularityRatioComparator.java
index f438762..1ed8e68 100644
--- a/main/src/cgeo/geocaching/sorting/PopularityRatioComparator.java
+++ b/main/src/cgeo/geocaching/sorting/PopularityRatioComparator.java
@@ -11,11 +11,6 @@ import cgeo.geocaching.Geocache;
 public class PopularityRatioComparator extends AbstractCacheComparator {
 
     @Override
-    protected boolean canCompare(final Geocache cache1, final Geocache cache2) {
-        return true;
-    }
-
-    @Override
     protected int compareCaches(final Geocache cache1, final Geocache cache2) {
 
         float ratio1 = 0.0f;