On Sun 2018-02-25 22:15, Dallas Hinton (1:153/7715) wrote to andrew clarke:

 ac>> Ah. I might not be able to do much about improving it as the code
 ac>> there is a bit of a maze.
 ac>> I encountered several crashes just trying to get it to work. :)

 ac>> But still, let me know if you can, so we can document it at the very
 ac>> least.

 DH> If I use the old version, a "next" scan (+) stops on Artware, which
 DH> is the first area with new traffic. If I use 1.3.1, the scan goes
 DH> right past Artware and several others and stops almost at random on
 DH> an area with new traffic (although it always stops there, so it's
 DH> not actually random!)

OK, confirmed here.

It's picking the wrong next area, but there seems to be a pattern to it in my
testing. I just don't understand why yet.

I've added that to the TODO list.

--- timEd/NT 1.31.g2+
 * Origin: timEd Development HQ (3:633/267.1)