Closed GoogleCodeExporter closed 9 years ago
Since not only D/T/size encoding has changed (back to where it was before
Christmas 2010), but also distance and direction are given verbatim again, -X
will only repair the worst misbehaviour.
It's kind of ironic that precise azimuths have become unavailable just a week
after merging the (issue 213) patch into trunk, but c'est la vie.
Here's a first version of a patch that supposedly fixes this issue, and makes
GeoToad fully operational again. I will continue testing (and if necessary,
improving) it, and prepare an "emergency release" within the next few days.
Development users, and other people willing to test the patch, please keep a
copy of lib/search.rb (or otherwise prepare to roll back)...
Original comment by Steve8x8
on 8 May 2013 at 9:35
Here's the patch, version 1
Original comment by Steve8x8
on 8 May 2013 at 9:37
Attachments:
Several tests showed no regression, so I committed the patch both to trunk and
branch (r1344).
Release(s) will follow next week.
Original comment by Steve8x8
on 8 May 2013 at 12:24
Phew, thanks for fixing so quickly :)
Original comment by trak...@gmail.com
on 8 May 2013 at 3:49
Release 3.16.7 is out, the bug will be closed as soon as 3.17.8 has been
released as well.
Original comment by Steve8x8
on 13 May 2013 at 10:14
Closing.
Original comment by Steve8x8
on 27 May 2013 at 7:34
Original issue reported on code.google.com by
Steve8x8
on 8 May 2013 at 8:46