[mkgmap-dev] Commit r4388: fix unlikely but possible error in LinkDestinationHook: Don't use HashSet() to collect Coord instances, use Collections.newSetFromMap(new IdentityHashMap<Coord, Boolean>()) to avoid that coords with equal locations are filtered.
From svn commit svn at mkgmap.org.uk on Wed Dec 11 11:08:10 GMT 2019
Version mkgmap-r4388 was committed by gerd on Wed, 11 Dec 2019 fix unlikely but possible error in LinkDestinationHook: Don't use HashSet() to collect Coord instances, use Collections.newSetFromMap(new IdentityHashMap<Coord, Boolean>()) to avoid that coords with equal locations are filtered. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4388
- Previous message: [mkgmap-dev] Commit r4387: fix unlikely but possible error in LinkDestinationHook: A way is only connected if the nodes are identical, so don't use Coord.eqauls() which compares the location.
- Next message: [mkgmap-dev] Commit r4389: fix unlikely but possible error in LinkDestinationHook: Can't use indexOf for coords.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list