OrderedTask, TaskDijkstraMin: optimise start point
commitedf16b4d8f3f2d59b3361cdf77f7a4f3132a6381
authorMax Kellermann <max@duempel.org>
Wed, 27 Mar 2013 08:15:03 +0000 (27 09:15 +0100)
committerMax Kellermann <max@duempel.org>
Wed, 27 Mar 2013 08:15:03 +0000 (27 09:15 +0100)
treea192e8c47e988f09cf02b2e63b1ab6c9373e2c2b
parent5d76a0b213b7814acc44629d6b6ce82bb03bd882
OrderedTask, TaskDijkstraMin: optimise start point

Allow optimising the start point by removing special-case code that
I'm not sure why it exists.  It leads to awkward
current_leg.vector_remaining values: sometimes, the vector points to
the reference point, and sometimes it points to the optimised
location.  Without the special case code, it seems to Just Work[tm].

The change to TaskDijkstraMin::DistanceMin() prepares the
GeoPoint::IsValid() check which may be added to other parts of the
task engine later.
NEWS.txt
src/Engine/Task/Ordered/OrderedTask.cpp
src/Engine/Task/PathSolvers/TaskDijkstraMin.cpp