What Changed in May 2019

What changed in January to April 2019

to Wednesday 24 April 2019

• Implemented a "Clear stops & pauses" option on the "new route" drop down menu - as suggested in issue 415.
• Made overnight stopping treat official moorings, and places with a mooring quality of "ok" ,"good" or "excellent" the way it already treated "havens". This means that it will use them for overnight stops even if they are in the middle of a lock flight or similar.
• Work on facility to add additional time to pass through designated places or links - source code additions

Thursday 25 April 2019

• Pre-release fix to bug where new places were appearing in linear maps as waterway ends (issue 590).
• Code to handle unicode escapes in strings being parsed from JSON (they are converted to UTF8) - this fixes issue 589 going forward.

Friday 26 April 2019

• More work on additional time. Source code tweaked and display code added. Now works as long as values are in the database.

Saturday 27 April 2019

• Continued work on extra_time: can edit times for places, and started on links. Improvements to the display.

Saturday 4 May 2019

• Fix to queued PDF to catch lost sessions

Sunday 5 May 2019

• Wrote code to purge place geodata for likely misparsed unicode escape and delete it - means issue 589 closes rapidly not only as the cache gets refreshed.
• Fixed an oddity I'd found where malformed waterway IDs broke the searcher
• Extra times log into the revision table and are displayed
• On release, ran the purge code

→ Release 9.32.16

Monday 6 May 2019

• Extra time is shown in outputs when not all places are being shown - both for places and for links

→ Release 9.32.16.1

Wednesday 8 May 2019

• Added extra time display to itineraries (which will include print outs)
• Multiple overnight stops display properly in itinerary issue 597

Thursday 9 May 2019

• Extended the overnight stops fix to PDFs

→ Release 9.32.17

Saturday 11 May 2019

• Added code to log and display changes to places
• attributes - logged and displayed properly
• bridge details - logged
• winding details - logged
• lock details - logged
• changeline - logged and displayed as code
• roadname - logged and displayed as text
• roadnumber - logged and displayed as text
• spur - logged
• postcode - logged
• mouth - logged

→ Release 9.32.18

Sunday 12 May 2019

In release 9.32.15.1 of Friday 19 April 2019 I started to collect additional geodata and said that when I had some I would work out a way to display it.

I've now done this; I've found a way now to add additional geolocation data to places without making the menu too clunky I hope. The new data items are – at the moment – What3Words, Geohash, MGRS, Maidenhead and Wikidata references.

Someone specifically asked CanalPlan to have W3W somewhere but it's not a feature request in the bug tracker as far as I can see and I can't remember where else it was. If you know, stick it in the forum or on Facebook.

Places that don't have a "more" button below "Date:" will gain one as the system acquires more data in the background.

As with the other geodata fields in this part of the menu, values can easily be copied by clicking and copying from the pop-up.

• Improvements to the "refresh place" function (which currently I'm about the only person who can use). Am considering opening it to other users (all or a subset) and needed to make it do things properly. Biggest improvement is that a pause then a second refresh to both remove the message and make it easier to wait.

→ Release 9.32.19

To Sunday 19 May 2019

• Ordered "books" (which includes maps etc) in output
• Fixed a bug in the alternative code calculations that had been introduced when I added the "extra time" functionality.

→ Release 9.32.20

To Wednesday 22 May 2019

• Created a simple test framework and built tests for "collapse" (which would have caught the error fixed in the last release) and width restrictions (for a bug I'm working on). Changed the language:
• a simple "die" with no parameters now exits silently without an error message, just a status (this was never used anywhere in the code base)
• You don't get errors with extra time for links that don't exist if you're restricting by boat dimension - one of those very messy things that involved passing another parameter deep into a chain of functions including as a parameter to a callback.

Thursday 23 May 2019

• Fixed the width bug reported in issue 601.

Saturday 25 May 2019

• Added format codes for place edit history following on from 9.32.18

Sunday 26 May 2019

• Prevented unchanged attributes appearing as a change.
• Attributes are now sorted when edited

→ Release 9.32.21

Monday 27 May 2019

• More work on the test framework to let web page generation be tested
• Fixed a bug where the duplicated places message didn't always show the place name

Tuesday 28 May 2019

• A small tweak to the logic - that took a lot of finding and then testing to see if I'd broken anything else - to address issue 603: a delay in showing some pauses in output

→ Release 9.32.21.1

• Improved rebuilding of short-form database and names table - issue 600.
• Turned on highlights and links in waterways gazetteer (issue 588) - don't know why they hadn't been on in the first place.

→ Release 9.32.21.2

• Allowed comments to be given for "impossible" moorings (surprisingly many changes needed to ensure this is collected and propagates) properly. Suggested in issue 388.

→ Release 9.32.22