Map Zoom problem

[RsH]

If I zoom in all the way on a route and delete one point the map stays zoomed in all the way and the area I am working on stays where I have it in my display. If, however, I select several points all around that one point, which are junk because the car was parked at that spot, but passing traffic caused spurious points to appear, and delete all of those points as a selected group, the map zooms back out to the starting magnification, and I have to zoom all the way in again. I HATE that extra step, over and over, as I get rid of the junk in a file when I have made a number of stops during the course of my local travels. I would much prefer the program to stay zoomed all the way in whether I remove one point or a bunch of points from the track. That way I control where I am looking in the file by simply clicking on a point in the listing on the right side of the screen, and then looking at that area of the total track to see if I need to delete one or more such points. Usually, with the GT-120, it is three or four points for each jog of the car due to a passing truck or bus, or whatever causes the unit to think it has moved. The ASUS R300 is less prone to that but still will jump to the right or left when I stop for a traffic light, so there too I might need to remove two or three consecutive points, and again the image zooms out again and thus once more I need to zoom in all the way. HELP!!!! In my view this is [!%!^@#&#$^]

[routeconverter]

I would much prefer the program to stay zoomed all the way in whether I remove one point or a bunch of points from the track.

I thought that is the case? Except there are no more waypoints on the map after the deletion, then it zooms out.

[RsH]

I would much prefer the program to stay zoomed all the way in whether I remove one point or a bunch of points from the track.

I thought that is the case? Except there are no more waypoints on the map after the deletion, then it zooms out.

No, that is not the case. There are No waypoints at all in my tracks... and what I do is zoom all the way in, click on position 1, and the map moves so that position 1 is centered in the display, and the beginning of the track appears. Then I use the page down key to walk through the route. I might find a place where there are several positions in a row which are really NOT the car moving, but the result of passing traffic, or a change in the reflection of the satellite positions due to tall buildings. I then point to each while holding the control key and then delete the bunch of them and the map zooms out. If instead I go to the LAST of those few points and delete one at a time it does NOT zoom out.... but that can be tedious. You can do this with any of the routes I've already sent to you, that do not have waypoints in them at all.

[routeconverter]

There are No waypoints at all in my tracks... and what I do is zoom all the way in, click on position 1, and the map moves so that position 1 is centered in the display, and the beginning of the track appears.

Hi Robert,

with waypoints I meant visible positions on the current map clipping... that refers to a problem I had when trying to fix this problem:

The last time I tried to fix the problem that the zoom level is changed when inserting or deleting more than one position, I stayed with the previous solution since it broke something else. Unfortunately I cannot remember what it was and the comment in the source code I had left doesn't give me a clue either.

Anyway, I've enabled the dubious code path again and could not find any bugs but I'm sure there are some Please give the latest prerelease 1.29.11 a thorough testing:

• removing lots of positions
  
• removing positions outside the current map clipping
  
• removing almost all positions
  
• saving and reloading files
  
• anything you can image
  

I'll do my very best to do the same but usually I'm pretty bad at finding bugs I've implemented.

[RsH]

1.29.11 seems to fix that problem, with the following 'issues', which may or may not matter to users. As I deleted, the map did NOT zoom out, but stayed where it was expected to be.

1. If deleting downwards, the position in the listing of points does not hold at the point where one has block selected a bunch of points to delete, but ends up about a screen full below that point in the list, so one has to 'backtrack' upwards in the list to get back to the last delete point. If deleting upward, from the end to the beginning, this was NOT a problem <grin> so I know how to get around the issue, but I am not certain why it is happening, and most of the time I prefer to go from the beginning to the end of the track, and not from the end to the beginning.

2. As I paged forward in the listing, to find the next point where some deletion was needed, the blue line that showed the track on the map sometimes was not there, even though the map itself moved. Moving back and then forward again to the same point using the page up and page down key always solved that problem, getting back to the same view of the same point in the map but with the blue track line the second time. Again, not a major issue, but the blue line also shows me where I may need to delete points due to tall building reflection issues or other causes of spurious readings that distort the route traveled.

[routeconverter]

2. As I paged forward in the listing, to find the next point where some deletion was needed, the blue line that showed the track on the map sometimes was not there, even though the map itself moved.

I have observed that problem, too. And I guess that's why I've left a comment in the code: it's a side effect of the optimized rendering which reduces the number of positions on the map to improve the rendering speed. Actually the area covered by the track should be nine times that of the currently shown map clipping.

[routeconverter]

1. If deleting downwards, the position in the listing of points does not hold at the point where one has block selected a bunch of points to delete, but ends up about a screen full below that point in the list, [..]

I modified the latest prerelease 1.29.12 to scroll to the position before the first deleted position to the top of the position table - that is the same behaviour as with the insert operation. Works fine for me since I usually process lists from top to bottom. I hope this removes another annoyance for you?

While at it, I'm now centering the map when changing the zoom level since most of the time I'd like to see more details of a selected position and not details of the position that happens to be the current center of the map. Does that make sense to you?

[RsH]

Both are fine and much better than the prior 'mess' that required my doing page up and page down and clicking to center on a point in the list. Time will tell if there are other problems [grin] but this IS definitely better.