Messages

[@slarti76]

@slarti76
ah!! Thanks for the video. I was talking and checking the behavior of the "Stop" button in the panel (as visible on the screenshot). You were talking about a small button directly on the main map screen.

As I see, the current behavior was implemented at 06/2022! and no complaints since then. Long-press simply calls "Stop" and the recording service takes care. In your case, seems you use auto-save, so the result is quick and correct from my point of view. Do you have some accidental clicks on this button?

Ah, ok - and now I tried long-pressing the button in the sidepanel, and it works as expected.

I could nit-pick that it's two red buttons with different long-press behaviour, but then again one has a square in it, which definitely means "Stop", and the other a colored circle. Let's say it's not 100% perfect, but I don't have a better idea, so let's leave it at that!
Thx for explanantion!

[@slarti76]

@slarti76
This simply isn't possible  .

Are we talking about the long press on this "Stop" button? There is a simple method that have to display "Discard" question dialog.

I'll prepare a video...

Sent by PM.

[@slarti76]

@slarti76
This simply isn't possible  .

Are we talking about the long press on this "Stop" button? There is a simple method that have to display "Discard" question dialog.

I'll prepare a video...

[@slarti76]

@slarti76
long-press to cancel recording > there is a confirmation dialog.

Doesn't work for me:
- Long-press when track has 0 or 1 point -> discard without warning (acceptable)
- Long-press for >1 point -> auto-save (without any interaction)

"Preferred folder" > this needs to be set for "Auto-save" to be working. But even if auto-save is disabled, the folder is pre-selected in the "save screen".

Ah, ok, then the folder makes sense, still - didn't realize that. I rest my case

That new "long-press-to-discard-recording" is a nice functionality, but has no security query - I don't think that's good. Could be accidentally triggered...

And another thing about recording profiles, probably not new, but just recently noticed:
There's the settings "Preferred folder" and "Auto-save after stop" - shouldn't the folder setting be grayed out when auto-save is off (and thus positioned below the auto-save slider)?

[@slarti76]

@slarti76
not exactly overlooked. I wanted to answer later and forget. Thanks for the reminder!
As I see in the code, this was modified at 31. 10. 2022 and it works as it should: the second part of the route should have time of this first trackpoint. Anyway, there is the condition when this is applied: "Created time" of the original route is identical to the first trackpoint. Is this your case? Otherwise app considers the original route time more important than trackpoint times and preserves it.

Thx for the answer, that condition actually makes a lot of sense. And it explains it: I did delete points at the beginning of the track before doing the split - then the condition was not met anymore.

Thinking about it, probably the best solution would be the additional option to sort by "track start date/time". I would even say that in 99% of the cases that's what the user actually wants when selecting "created by". Why would you sort a self-recorded track and an imported track differently, just because the imported track has a later creation date, even if it's chronologically ealier?
Is adding that sort criteria feasible?
Of course, the workaround is to always *first* split a track before doing any other editing - but obviously I hope you agree with me that "Track start time" is a good thing to add

Little weird observation in my recent holidays:
I split a track A into A1 and A2. Then both tracks had the same creation date/time (I think we discussed this a while ago, before that both parts got the current DT as new creation dates). Now when I sort the folder by "Created", it shows

• A1
• A2

- correct!

But when I reverse sorting, it still shows

• A1
• A2

- not really correct, as the second part of the original track is surely after the first part and thus should be shown before in the reversed list.
I assume, as both tracks have exactly the same created date/time, Locus then reverts to alphabetic sorting as "tie-breaker", which keeps A1 before A2.

Proposal:
As we agree that it's not helpful to set the Created DT of split tracks to the current DT, why not set the DT of the second part to its first trackpoint?

Hi Menion
Don't wanna be annoying, but you answered a lot of posts, but no reaction to this - overlooked, perhaps? Thx!

I think we discussed this a while ago

Yes (search for "split"), we did, you did, I thought it's all sorted 😁.

Yeah, there's always a special case to be overlooked 

Little weird observation in my recent holidays:
I split a track A into A1 and A2. Then both tracks had the same creation date/time (I think we discussed this a while ago, before that both parts got the current DT as new creation dates). Now when I sort the folder by "Created", it shows

• A1
• A2

- correct!

But when I reverse sorting, it still shows

• A1
• A2

- not really correct, as the second part of the original track is surely after the first part and thus should be shown before in the reversed list.
I assume, as both tracks have exactly the same created date/time, Locus then reverts to alphabetic sorting as "tie-breaker", which keeps A1 before A2.

Proposal:
As we agree that it's not helpful to set the Created DT of split tracks to the current DT, why not set the DT of the second part to its first trackpoint?

In the news it says:

"more accurate contour lines – in the new LoMaps we generate more detailed drawn contour lines from 1" height data, while maintaining the volume of map files. We have completed Europe so far, but the machines are running at full speed, so you can look forward to further additions soon."

Does this work for existing (already downloaded) HGT files or do they need to be downloaded again? If so, does Locus do that automatically? Or is it a map feature independent of teh HGT files?

... after examing all settings I saw that the text size was set to 0.
Change to 100 produces a better result:

That's what you call a better result? 

I do see the complexity in combining all searches together, and I can live with having to select different search "means". But one major bother, that should be not too difficult to change is this:
Everytime the search scope is changed, there's a new, empty input field. Why not prefill with the search term already entered in another search? All the time I start typing into a search field before realizing I have the wrong search - then I change it and have to start from scratch (unless I thought of that and copy-pasted the term, which of course is also a bother).

PS: I just realized that this works between internal point and track search, but that's the only place I found.

[Problem with SRTM/HGT:]

Problem with SRTM/HGT:
I downloaded some 1" elevation data from here: http://viewfinderpanoramas.org/dem1d.html
...

Go for Sonny's LIDAR DTMs instead. Much better than SRTM.

Thx, seems to work with that. Still perhaps worth looking into whether the (other) data is buggy or Locus...

PC browser goes to GD folder from Aug 2nd, version 4.18.0, not 4.18.1, even on PC.
Or do you have a MAGIC link instead :-) ?

Sorry, my bad, didn't see it's about the .1

I'm missing the 4.18.1 AFA on GD, Menion.

Me too ...
The link is present, but doesn't work.

Had the same problem on phone, but worked on PC browser *headscratch*