Canalplan Bug Tracker

Anonymous Login
2019-06-19 18:44 BST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0000451Canalplan [All Projects] Bugpublic2019-05-18 16:30
Assigned ToNick Atty 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionno change required 
PlatformMacOSmacOSOS Version10.13.4
Product VersionProduct Build 
Target VersionFixed in Version 
Summary0000451: Lock Count Error
DescriptionDay 2 starts with 1 lock. It looks as if it is assumed that you stop at Fradley Visitor Moorings, which I did, and not after the final lock.
TagsNo tags attached.
Attach Tags (Separate by ",")
Attached Files




Nick Atty (administrator)

It's not an actual bug as such, more a design decision that doesn't always do what people expect. Day one finishes *at* the lock, not just past, so it doesn't count it until the next day. Even though, obviously, you can't actually stop "at" a lock.

Something similar happens if you plan a trip to or from a lock - the lock doesn't actually appear in the totals - it always assumes you are on the side you set off from.

If you look at the rest of the route you'll see that all lock passages are calculated like that - the lock doesn't count on the stage where you reach it, but on the one where you move on from it.

I'm reluctant to change anything here as the overall totals are right (the lock is counted once in the two days put together), and since you won't actually stop in the lock overnight(!) it will give the right numbers for where you might actually stop - which is what all the predicted stops are about, really.

If you can think of a better way to do things, that won't be just as confusing in the other direction, please let me know.


Autoclose (administrator)

Closing automatically, stayed too long in feedback state. Feel free to re-open with additional information if you think the issue is not resolved.

-Issue History
Date Modified Username Field Change
2018-04-25 08:27 MikeS New Issue
2018-04-25 08:27 MikeS File Added: Lock Error.pdf
2018-04-25 11:01 Stephen Atty Assigned To => Nick Atty
2018-04-25 11:01 Stephen Atty Status new => assigned
2018-05-12 10:09 Nick Atty Note Added: 0001768
2019-04-18 16:21 Nick Atty Status assigned => resolved
2019-04-18 16:21 Nick Atty Resolution open => no change required
2019-05-18 16:30 Autoclose Note Added: 0002453
2019-05-18 16:30 Autoclose Status resolved => closed
+Issue History