This object is in archive! 

Need help for hiding/revealing tracks.

Taras D shared this question 5 years ago

Here's what happens:

  1. I display a track.
  2. I exit and restart Locus Map (Pro V3.26.2)
  3. The track is not displayed. It is hidden.

Sometimes the opposite happens:

  1. I hide a track.
  2. Exit and restart Locus Map.
  3. The track is displayed. It is not hidden.

A track's visibility (hidden or displayed) should be saved from one session to another, yes? What am I doing wrong?

Replies (2)


Good evening Taras,

are we talking here about tracks from internal database? If so, what you mean by "exit and restart"? You're just playing with app and quickly close and open it? Then don't do it or at least between close and open, wait at least 5 seconds and tell me result ...


Yes, existing tracks in the internal database.

Initially I had the New York OpenAndroMap displayed with one recorded track and three routes I had created with Route Planner. I hid each one (using the popup menu) and then exited Locus Map. I'm sure the session lasted longer than 5 seconds. When I restarted Locus Map, the track and routes were visible again (should be hidden).

I tried to hide them using other available techniques but the result was always the same (they reappeared).

Finally, I switched from OpenAndroMap to New York LocusMap, then hid the tracks and routes. When I restarted Locus Map, the tracks and routes stayed hidden. Great! I thought I found a clue ... but now I'm not so sure.

I displayed a few routes (on the Locus Map), closed the app and when I restarted it, the routes were gone (should be displayed). I guess switching maps isn't a clue.

I just repeated the experiment and waited 15 seconds before closing Locus Map. It made no difference. The track failed to be displayed.

I think I might have discovered a proper clue. I am not using the menu command ("Exit") to close Locus Map. I display Locus Map in immersive mode, so I normally sweep up from the bottom to display the three on-screen android buttons, tap the "Recent Apps" button (android's right button) then drag the app-window off-screen to the right.

I repeated the experiment using the "Exit" command, then dragged the app-window off-screen. When I restarted Locus Map, the track was displayed.

I will try this again several times to make sure it is repeatable.


Yes! It's repeatable! If I use the "Exit" menu-command, it always works correctly. A track's visibility is correctly retained from one session to another. However, if I exit by using the technique I described above (in immersive mode, sweep up from bottom to show "Recent Apps" button, tap it, drag app-window off-screen), Locus Map fails to retain the track's visibility to the next session.

Maybe it's not getting the correct "shutdown signal" from Android? So it doesn't get the opportunity to save some session settings like the track's visibility?


I'll look at it, thanks for experiments.

Btw. there is nothing like "shutdown" in Android ;). App lives lives lives ... and then suddenly die without knowing it ... weird Android world.

And by 5 secs I wrote before, I though interval between closing and re-opening app.


It looks like nothing has changes after all these years.

I was searching a lot to find some solution on a simple question: how should application react on "swipe out in recent list" action. And there is still single answer: "it is not possible".

Locus (or generally any application), has no chance to catch the right moment, when it's swiped out from this list. Anyway I've improved system a little bit, so after every change in visibility of Locus itself, Locus check if points or tracks has some new state and save it if possible. Believe it will solve this problem and do not bring and slowness etc. Let me know, if in next version it will work fine for you, thanks!


Thank you! I look forward to trying the next version.

Replies have been locked on this page!