Messages

You are aware that Locus Map Free (LM4 alpha) and Locus Map Pro share the same data right?

yes

Isn't possible that you restored the backup/database in Locus Map Pro?

do you mean sync? I haven't restored any backup. LM3Pro doesn't have any sync function right? I don't it's possible.

this should not happen with the latest version without user confirmation

is it possible to delete all cloud sync data before I retest? or what do you suggest I test next?

May you please share (privately or the public, no sensitive info inside) "Locus/data/database/sync.db" file?

I've emailed you the file. Thanks.

wait, "hiding of the side panel does not work"? You seems to have recording button at the bottom and "Bottom panel visibility" settings does not work for you?

sure "Bottom panel visibility" auto-hide works, but I was hoping retain LM3 Pro layout/ behavior - hide this new & redundant red record button which is only visible while recording, not all the panel buttons, and especially not the green track recording button; at present there is a show| auto-hide| hide setting for all main screen components except the map screen content button & red record button; but let's park this discussion for now

Auto-zoom: it is not fixed to 20%. I wrote "up to 20%", so it already dynamically increase.

20% is not much, but again let's park this discussion for now, you have much bigger fish to fry

"Save actual part" is wrong English, it must be "Save current part". Well, unless Andrew (or some other native speaker) disagrees with me here...

sure - better, but there are many other places too

[@slarti76]

@slarti76
Duplication: hmm, there had to be something that caused this problem! Your first and second sync were from the same device? There was no restore of the old manual backup between sync?

1st & 2nd sync were from same device - I only have LM4 installed on 1 device; "about" 2 weeks apart; no restore in between the 2 syncs; I haven't tried to sync again (risk) but next time I will do a full backup just before a test sync because this caused lots of work & nearly lost some data that was created in the 2 week period. Happy to continue testing but waiting for your advise.

[@freischneider]

@freischneider
hmm, like that this recording button should be visible on the screen permanently, or with a possible "auto-hide" option. Hmm, this would solve the "duplicate button" problem mentioned by Andrew, an interesting idea, thanks.

"Green dot in recording button" to indicate currently running recording ... interesting idea, I'll think about it, thanks!

yay!

Recording button: is there any more important button then the button, that clearly informs about running recording? Understand about redundancy ... is it really a problem? Expect you usually hide the side panel with the recording button.

agreed, most important button/ indication; redundancy - waste of screen space; OK - so main issue may be that hiding side panel doesn't work - which setting?

Sync: "from a long period of time" > how long? Not too many users use this feature and it sometimes happens, that server is put to "sleep" and take a while (30 - 60 sec) till he "wake up" . Anyway no data are sent twice, but it is possible that the app sends some metadata about all data to verify, nothing has really changed, so it makes take a few additional seconds.

how long - 40 minutes! not too many users - sure because it's LM4 beta right? The biggest issue since my previous comment is that all tracks/ points/ folders/ groups were duplicated during the 2nd sync. Really bad news for me. You already comment here thanks.

"Turn on getting location" ... weird, never saw this text wrong. Does it happen always?

as I said Not seen before/ rarely happens.

"rescale value" from config.cfg ... well, It is not yet implemented. What still works are only some components that are shared between Classic and Map version, sorry.

So buttons at bottom don't rescale, but right side panel buttons can rescale?

Improvement in auto-zoom: this is already "partially" implemented. During navigation, when you get closer to your next navigation point, the app increase auto-zoom settings for up to an additional 20%.

nice start but 20% isn't that much improvement. Auto-zoom could commence direct after previous navigation point, and not fixed 20% but dynamic increase (within limits) so that next point becomes visible.

About 2 weeks ago I tried a manual cloud/sync for 1st time. Just 1 device. I assume it was OK - no errors.

So yesterday after a few more tracks & points I tried another manual sync. I was expecting the process to be fast because there were only 2 weeks of new tracks & points, but 40 minutes later I find that LM4 has created duplicates of every track, every point, every folder, every group.

Naturally this was quite annoying because A) when you delete a group you still have to delete each folder within the group, there is no option to delete all at once B) I then had to carefully pick which of each pair the latest changes, if any, were in, and delete the other. In one case I made a mistake & had to import.

Cloud Sync > tap More Info button > there is less info (no date/ time), but mainly same info on bigger screen.

A few general comments:

• See attached screen cap where satellite screen says "TURN ON GETTING LOCATION" but is clearly already turned on. Message is opposite to state. Subtle timing error? Not seen before/ rarely happens.
• I use config.cfg dev_gui_main_rescale_value=1.1 to increase the size of buttons. Very useful with gloves when cycling. I notice the top/ right panel buttons are rescaled correctly, but the bottom buttons ignore this setting. Any reason? See attached screen cap comparing 3.49 Pro (correct) & LM4 (ignored). Also would it be possible/ useful to move this setting to Expert Settings?
• See attached screen cap for Zoom settings - text at bottom is missing. I tried panning the screen but no movement.
• I have a new idea for auto-zoom. I'll post here for any comment 1st. Maybe a help suggestion topic. As a cyclist I never use auto-zoom. Unlike a motorist my speed is mostly unrelated to required zoom. But maybe while navigating, within constraints, zoom could be optimized such that the next {nav/ via/ POI} point is made visible? So as I get closer to the next point of interest the zoom dynamically increases. At the moment I do this manually anyway while navigating. I could expand on the idea in a topic if you think it has potential.

Record button color: It is common for the color to be red. That's why it should stay that way.

@freischneider - the track record button is green in LM3/4. It has been for > year or more.

I find it useful to visually scan "state" buttons - satellite, track record, POI, Live Tracking, and see that all green means all on/ all OK.

bug: settings > Track recording > Style of tracking recording panel: change setting - not updated in menu after option is tapped

red track recording button: I recall years ago a similar discussion with LM3 - is there a setting for this red button be always hidden? It's redundant if the other (green!) track recording button is included in a panel. I tried setting > Track recording > Panel auto hide, but it made no difference. There was also historical discussion to change track recording button from red to green. I like always having the button displayed as reminder whether recording has been disabled, but not two buttons, and not one that auto hides.

settings > More functions > Use magnifier, or settings > Use magnifier (if set) - would it be more use to return immediately back to the map after this function is tapped? At present there is no user feedback after the Use magnifier button is tapped, so no indication magnifier has been toggled, which is a little confusing.

Regards cloud sync: I successfully sync'd my data a few weeks ago. Only a few items have therefore changed since, but when I try this function again now, it appears (from the long period of time) that all the data is being re-sync'd. Isn't this supposed to be a transfer of only changes since last (manual) sync?

Crash: nothing un-usual on the GPX file.I've tried it and no problem, so please if this still happens, create a log by common method. Thanks!

thanks for checking the GPX file; I've emailed you the report

The crash is 100% repeatable in LM Pro 3.49, it didn't happen in LM Pro 3.48. Unfortunately it happens in LM 4 3.49.0.2_967_beta too although it was a few announcements later. But it is always just after a navigation announcement.

[2]

The new directory for custom profiles should be "Locus/router/profiles". This directory should be already created by Locus Map upon start. Old Locus/data/brouter directory is no longer used.

Thanks for reply. I can see an empty Locus/router/profiles2, but no Locus/router/profiles directory. Directory datestamp is yesterday 28/10/2020 when I upgraded to 3.49. I also assume Locus has copied BRouter BRF files into Locus/data/brouter/profiles2. Directory datestamp is 15/4/2020. This is quite confusing. Should Locus move all Locus/data/brouter/profiles2/*.BRF to Locus/router/profiles/? And if the former directory is now empty, delete that directory?

I moved one BRF from Locus/data/brouter/profiles2/ to Locus/router/profiles2/ & this is displayed in profile list. So are you sure you mean /profiles, not /profiles2?

I created a short route yesterday (GPX attached) to test another issue, but Locus 3.49 crashes very shortly after I start navigation along the route. There is one navigation command announced then crash. I've never seen a navigation crash before. Can I send more info?

PS. I have just used a long route for which navigation was working in 3.48 but now crashes in 3.49. So this bug is related to 3.49 (or my configuration), not something strange related to the route.

Please remind me how to view my BRouter BRF profiles in the Navigation > BRouter settings > Routing profile list?

I can confirm the BRF files have been coped
from /brouter/profiles2
to Locus/data/brouter/profiles2/
and from the spanner menu I have Advanced settings checked
but the Routing profile list only contains built-in Locus profiles.

My profiles that had used BRouter have all been set to Car-Eco.
Won't this be an issue for anyone that used BRouter profiles in 3.48?