[APP] - version 3.48.+ ( 28. 8. 2020 )

Menion · August 31, 2020, 16:07:03

Important links
- list of news of public versions

Versions
28. 8. 2020 - Locus 3.48.0
10. 9. 2020 - Locus 3.48.1

Tapio · September 01, 2020, 08:47:08

"Select all" in file browser (gpx import to folder) seems to select subfolders as well, resulting in "same filetype" error message.

Menion · September 01, 2020, 11:09:42

Ah, thanks Tapio. Got it, will be fixed in the next version.

balloni55 · September 05, 2020, 19:43:03

backup mystery...
my setting: backup every day, keep 2
today i´ve got 3 messages (10:01, 16:30, 16:58) "Backup not sucessfull"
first two backups are stored, are they ok??
but they are not recognized, so i get third message

tramp20 · September 06, 2020, 06:35:38

Quote from: balloni55 on September 05, 2020, 19:43:03
backup mystery...
"Backup not sucessfull"

I noticed this errors too.

balloni55 · September 07, 2020, 07:40:40

Please add new attribut icons to GC-filter list
https://www.geocaching.com/blog/?p=79169/?newsletter=PM

Tapio · September 11, 2020, 09:02:10

"Backup not successful" notification. Unfortunately I swiped it away. I see a working zip file from this morning, it seems OK.

tramp20 · September 11, 2020, 10:44:36

With this new version 3.48.1 I get always a crash (free and pro on Android 10, Android 5.1.1 is ok) when I close automatic backup - settings even without changing something.
I sent two feedbacks today

Menion · September 11, 2020, 19:58:11

Thanks @tramp, based on this and also the second problem with crash after adding the WMS map, I've today published one more version: 3.48.2. Tested so it should work correctly now.

@balloni55
thanks, the TODO list for geocaching is growing and growing ...

Some problems with backup ... there should be minor update in current version in cases, you get backups more often then planned. Anyway I still did not observe any "unsucessful" message ...

tramp20 · September 12, 2020, 08:31:36

Quote from: menion on September 11, 2020, 19:58:11
Thanks @tramp, I've today published one more version: 3.48.2. Tested so it should work correctly now.

Thank you, no more crashes with automatic backup - settings.

tramp20 · September 13, 2020, 10:30:07

Quote from: Menion on September 11, 2020, 19:58:11
Anyway I still did not observe any "unsucessful" message ...

Today again but this time without a backup.
The other times this message came with a correct backup.

Andrew Heard · September 14, 2020, 01:28:59

Today I had to rely on restoring a backup while diagnosing lack of DEVICE ADMIN APP security settings for display on/off control while navigating. I found (unrelated to my main task) that Navigation > "Link with preset" settings are not restored. Maybe a bug?

Andrew Heard · September 14, 2020, 03:17:42

Bug - untranslated string: "T:Invalid source parameters": 3.48.2 Pro. Probably not related to latest version.

From Route Planner: I was trying to create a test route with navigation commands every 10 metres where I could subsequently set the command to be one of the 10+ directions for testing my own TTS ZIP. I get an error that distance between points (10m) is too short. This is OK, but then on undo, I get the untranslated string: "T:Invalid source parameters".

Tapio · September 19, 2020, 07:15:33

"Unsuccessful Backup" notification. 2:01 am. But there is a zip file from 2:01 and it seems OK.

slarti76 · September 20, 2020, 11:23:05

One little improvement for the Track Editor:
Menion, you might remembered some years ago we discussed about the "timestamp-recalculate" feature of the Track Editor?! For those who don't know: In the Track Editor ("Modify Track"), when using "Insert/Edit trackpoint", moving track points will also change their timestamps. For adding trackpoints, it's obvious that a new time has to be calculated. Now when moving existing points, Locus will also recalculate the timestamp based on the new distances. In principle a useful feature, but I always disagreed with Menion about existing points (and I would still like to see a switch "Auto-Recalculate On/Off" in the track editor).
Anyway, we found a (kinda hidden) compromise: When only moving a single point, Locus will not touch its timestamp. So there's a slightly hidden possibility to edit without touching the timestamps.

Now my request concerns gaps: Currently, that recalculation also takes place across gaps. But I think you wil agree that gaps are there to separate different sections of a track. So assume we have the following points:

12:00.00
12:00.10
gap
12:10.00
12:10.10

Currently, if you move points 1 and 2, the time difference between 2 and 3 will also be smoothed. The exact result of course depends on the actual location, but we might get something like 12:00:00 - 12:05:00 - 12:10:00. I think you'll agree that this is wrong.
So would it be possible to never let your recalculation "extend over" gaps? Even if you edit 1,2 and 3, points 2 and 3 are effectively end and start points of a section and should therefore keep their timestamps.
Agreed?