Can not select another track after track modification

tkansgar shared this question 6 months ago
Answered

Hi,


when I just have modified a recorded track, I sometimes can't select any other track to modify it too. The map screen ignores any tapping on it. This is so since two or three new versions. But unfortunately it is not surely reproducable. The new track modify screen sometimes has a similar behaviour. When I have modified one end of the track I can't select a point on the other end of this track.


Kind regards

tkansgar

Comments (12)

photo
1

Hi Tkansgar,

if there's any such issue two - three versions back, we would have surely known about it. I tested it, to be sure, again on my two devices (Xiaomi Mi3

and Nexus7) and couldn't simulate the issue. I'm sorry we can't help if we can't simulate the problem.

photo
1

Hi,


as I mentioned before, I can't surely reproduce this issue. I will try to find a way to do so.


My Smartphone is Samsung A3 2016 with Android 7.0.


Kind regards

tkansgar

photo
1

Hi again,

with the newest version I can't reproduce this issue any more. Hopefully it's gone. If it comes back, I will post it here.

Kind regards

tkansgar

photo
1

Hi again,

it came back in last weeks, But now I got the new version 3.28.0 and just removed some track points. Seems, that all problems I had here are gone. One of them I hadn't mentioned here until now: After modifying a track, leaving the track editor and zooming out all the map tiles of my downloaded map except that one, where the modification was located, were gone. I had to load an online map and to reload my downloaded map to see its tiles again. This bug also has gone in the new version.

Many thanks, Menion, for this great App!

Kind regards

tkansgar

photo
1

Hi,

this issue is back again. Here is my way to reproduce it (I try to give the english texts, but they may differ here; I only know the german translations):

  1. Go to the map selection screen and choose a locally stored offline map.
  2. In the map screen tap on one of several contiguously displayed tracks.
  3. A list of several tracks appears. Select one of them.
  4. In the box displayed now tap on the arrow and then on "Modify track".
  5. Close the appearing tool box with the hardware back button (on many Samsung phones bottom right).
  6. Tap one or more times on one of the two blue arrow buttons bottom left to go to another track point.
  7. Tap on the pencil in the box to display the tool box again.
  8. In the tool box choose "Remove all before (or after) mark".
  9. Now tap on the check mark top left to confirm the modification.
  10. Now try to tap on another point of the same track.
  11. It's not possible to perform another modification of this track here.
  12. Use the hardware back button to leave the track modification editor.
  13. All the other tracks appear again on the map screen.
  14. Zoom out with the Minus button several times.
  15. Now you see only the single map tile where your last modification took place. All other map tiles around are gone.
  16. Go to the map selection screen and choose an online map.
  17. Go to the map selection screen again and choose the same locally stored offline map as before.
  18. Now all the missed map tiles are back again.
  19. And now you can modify the same or another track again.

When I exactly follow these steps, I can reproduce the bug each time. May be if you miss one of them, you cannot.


Kind regards

tkansgar

photo
1

Hi tkansgar,

I've tested your procedure several times but to no avail - I can't simulate the issue. Maybe I've got a comprehension problem with points 2 and 3 - when you click one of a group of tracks on map, only the track popup appears, not a "list of several tracks". The same, point 12, "Use the hardware back button to leave the track modification editor." - using hardware back button twice leads to closing Locus (however, depending on settings). Etc.

Lastly, the whole procedure is so complex that it can't be reproduced the same way on all android devices and OS versions, therefore, I'm afraid, attempt to "fix" it would not lead to desired solution.

photo
1

Hi Michal,

to points 2 and 3: Most of all my tracks start and end at my house door. So these track ends on map lay very near by. When I try to tap on one of these ends, I each time hit more than one track. So Locus Map displays a list to let me select the track I have meant. I could try to find an alone displayed track line somewhere on the map. But then I had to make an unwanted modification to that track.

To point 12: At this point I'm still inside the track modification editor. I can see this, since only the just modified track is visible, not all the others. So I'm not about to close Locus Map at this point. Did you press the hardware back button between points 9 and 12? Then you did it too early.

Next time I have a track to modify I will try to find a workaround for this issue.

Kind regards

tkansgar

photo
1

Hi tkansgar,

thanks for the clarification. Now I went through all your procedure points correctly and exactly as you described. But no issue appeared. The track remained editable, the map tiles displayed correctly after zooming out. I'm sorry, I can't help.

best regards

Michal

photo
1

Hi Michal,

I just tried some variants of my procedure above. And it seems, that the issue only happens, if I modify a track recorded by Locus Map. I could not reproduce it with tracks I created on GPSies and imported to Locus Map via my PC.

Another point seemed to be this: Normally, if a track has been selected to modify, that track is marked by Locus Map to be modifyable now (by displaying the track with another line style). But sometimes this marking doesn't appear. Until now I could not find out, how this can be surely reproduced. But this little bug seems to be independent from the issue above.

Kind regards

tkansgar

photo
1

Hi Michal,

now I found another condition, which must be met to get the issue: You must use one the two functions "Remove all before mark" or "Remove all after mark". When I use the last function of the toolbox removing only the actual track point, all is fine. And one step of my previous procedure can be ommitted: It's not necessary to select a track out of a list of several hit tracks. Here is my new complete procedure to reproduce the issue (completed by another aspect of the same bug at points 13/14):

  1. Go to the map selection screen and choose a locally stored offline map.
  2. In the map screen tap on a track recorded by Locus Map.
  3. In the box displayed now tap on the arrow and then on "Modify track".
  4. Close the appearing tool box with the hardware back button (on many Samsung phones bottom right).
  5. Tap one or more times on one of the two blue arrow buttons bottom left to go to another track point.
  6. Tap on the pencil in the box to display the tool box again.
  7. In the tool box choose "Remove all before (or after) mark".
  8. Now tap on the check mark top left to confirm the modification.
  9. Now try to tap on another point of the same track.
  10. It's not possible to perform another modification of this track here.
  11. Use the hardware back button to leave the track modification editor.
  12. All the other tracks appear again on the map screen.
  13. Now try to tap on another track.
  14. It's not possible to perform a modification of any track here.
  15. Zoom out with the Minus button several times.
  16. Now you see only the single map tile where your last modification took place. All other map tiles around are gone.
  17. Go to the map selection screen and choose an online map.
  18. Go to the map selection screen again and choose the same locally stored offline map as before.
  19. Now all the missed map tiles are back again.
  20. And now you can modify the same or another track again.

As I wrote before, my phone is a Samsung A3 2016 with Android 7.0. May be on another device this doesn't happen.

Kind regards

tkansgar

photo
1

Hi tkansgar,

tried it with my personal recorded running tracks - no problem. The same with highlighting a track in track editor - always highlighted.

photo
1

If this happens only on the device you have, it's also not processable - there are thousands of Android devices on market and we don't have capacity to tackle an issue that takes 20 (!) steps to perform on one of them. Again, sorry.