Messages

[@slarti76]

@slarti76
Currently, it is ... correct. App by default specifies a background color that matches the current mode (dark/light). Anyway, there are maps (mainly vector maps with "theme") that have their own definition of the background color. And this is used no matter if dark/light is selected. I was thinking about working with this color as well, but I'm sure that preserving defined background color for vector map is the ideal solution.

Ok, as I said, it's fine with me, was just confusing at first.

1sec delay ... always? There was no change in the latest versions ...

Yes, on my S9 and Tab S5e the speed is normal, but on the XCover Pro it's always a lag of around 1s. I know it's a slower phone - but it's only the main menu... I think it's not new as such, may have been like that since Locus 4 (don't have LM3 installed there anymore, but I'm sure it was never that slow). Could it have to do with the "Gold" Status? Perhaps there's an additional query every time the menu opens?

Also, the "Map-screen content" sidebar visibly first opens a narrow white strip before the whole thing opens. Perhaps 50px wide. It's definitely not a "move-in effect", it's not smooth, and it's noticable on all my device (with differing speed, though).

I tried to do a screen recording, but you can't see when I tap anything, so it's not that helpful...

Weird: Now (latest Beta) my map background when loading is first black for online and external maps, but white for vector maps. I'm fine with both, but it's inconsistent.

I also for a while notices an almost 1s delay when opening the main menu on my (slower) smartphone. Anybody else have that problem?

[@slarti76]

@slarti76
Hmm, at least check please expert settings > Map rotate only when centered.

Uh, yeah, I totally didn't see that. With that setting off it works as expected. Thx!

I bought a new bluetooth button for my bike and set the correct button codes in the expert settings. Works fine, I can zoom with the button, switch map centering on/off and rotation. However, if map centering is not on, rotation has no effect. Well, the compass icon appears, but it just points north. This state (compass icon shown, but centering button is white inside) cannot be reached with manual taps, as far as I can see.

I think this was discussed before, some people would like to see rotation even without centering. I tend to agree, but even if the result of the discussion was "No", then at least the compass icon shouldn't be shown in the above situation.

PS: In the expert settings for the HW buttons, it says "Map centering on/off". But the actual action is only "Center map". I mean, nothing is turned on, it just centers the map once. Shouldn't this set "Hold map center"? I would much prefer that for my button, perhaps it can be added?

I like the way they calculate the ETA, it's something Locus (app and web) needs to improve.

I'm not sure what they're doing there, but nobody, really nobody who regularly hikes or bikes would think in this way. The usual way to think is "300m up/hour, 500m down/hour", something like that. I don't know how many meters I have to go forward while going 1m up? And then measure this with 2 decimal places (1m up is 7.92m forward)
Maybe a nice UI, but please no such nonsense in Locus. Perhaps you can calculate well with these inputs, but your result will be as bad as your input is.

[Switch track and point details]

Two more things:

Switch track and point details
I like that you can now switch back and forth, but it's not intuitive. It would be best to have the button switch from point to track in the lower left. I see the problem that then the point buttons are different for trackpoints and POIs. But for me, that would be less important.

Deleting in Track Editor
I still have the problem that in Track Editor, after deleting several single points or sections, at some point the track disappears and I have to leave/re-enter Track Editor.
Menion, sorry I always have to bring this up

[MapGooglePlay_4.0.2.3_1007_beta]

Hi guys,
new version MapGooglePlay_4.0.2.3_1007_beta ready for weekend testing.

Well, played around with the syncing, back and forth, Route Planner, Track Editor - couldn't find any wrong behaviour whatsoever! 
Thx a lot, happy you could squash this bug!

Just one tiny thing about auto-sync again: Somehow my tablet doesn't always notice there were changes. Two situations:

• Locus stopped on tablet, editing a track on phone, syncing; then start Locus on tablet: No auto-sync, have to sync manually. This I can reproduce on the tablet, but the other way round it seems to work.
• Locus running on both devices, screen on. I edit on phone, sync, but no auto-sync on tablet. I think it worked once or twice, but I'm not sure. The other way round, it always works.

No idea what could be different. Only thing that comes to mind: My tablet is always in flight mode (no SIM), but with WiFi active (I know, it probably makes no difference, just superstitution that might save some battery). So if auto-sync doesn't run when flight mode is on, not looking at the WiFi state, that might explain it.

But apart from that, I'm happy now 

Ok, more tests with new beta.
Good news first: Turning on auto-sync now leads to initial sync. Thx

But my big sync problem and the crash-when-clicking-on-track isn't resolved. In fact, I can reproduce the sync problem now:
Turn on auto-sync, take a track (created with the route planner), sync it, now edit the track (on A) with the route planner, save (overwrite), wait. After auto-sync is through on both devices, the track will be gone on B. Reproducible. On A, the "Last Update" shows "pushDelete: 1", no "push".

Now the funny thing: this time, further manual syncs on both devices didn't lead to the track being deleted on A, instead at some point the track actually appeared on B! Still, not trustworthy.
Also, I could now click on the track on both devices without crash.

But... Now I wanted to try it with Track Editor instead of Route Planner. Again, edited on A, clicked the track - crash. Synced to B, clicked the track on B - crash. So after editing with Track Editor, sync seems to work, but track detail popup crashes Locus again.

Hope explanation is detailed enough.

Oh, and for the crashes: My User ID is 6880a91b7.

Trying out new beta, unfortunately track description is not selectable/copyable anymore.  Any reason why this was removed?

Beta 4.0.21 version hard crash - but not reproduced yet:

- I created a track with the Route planner with only shaping points
- Saved it
- Opened it again, moved some points
- Saved again.

It was visible on the map. When clicking on it, Locus instantly crashed, Did not manage to open the new track screen. Locus crashed any time I clicked on this track.
Unfortunately I made a mistake and didn't export it, now it is deleted.

That's basically the same that happened to me, just with the addition of the sync problem (which obviously doesn't apply to you, as you made a new track). With me, the track edited with Route Planer also made Locus crash on click.
Menion said he's gonna have a look at it, so fingers crossed he can reproduce...

"Right arrows": ugh,not a designer, will think about. It's not a problem but my guts say there's a better symbol.

What about three points in a box (button) - better shows we're changing to a new screen. Perhaps keep the arrow: "...>"

Back from trackpoint: I mean we cannot go back from new trackpoint screen to new track screen. Fore and back...

My point precisely Would prefer consistency here...

[@slarti76]

@slarti76
Track screen
- selectable title? Eh, ble. Just open "edit" when you need to copy it.

Yeah, OK. Copying (potentially longish) description was much more important, thx for that.

- description below the title is currently not ideal. What you need most at the top is definitely a chart. I do not consider one small swipe up to reveal description as a problem.

See your point. Still, please consider the "2 lines, can be expanded with extra click". Description could be very long and then the pull-up screen would also be very long here.

- customization is the last step, as usually

Sure thing, take your time. Was just writing down everything that came to mind about the new screen.

- back from the trackpoint: there already is a visible panel with parent track and the right arrow button takes you back

Ok, but right now it takes you to the "old" screen. If the plan is to replace that with the new pull-up screen, then all fine. Not sure what the plan about the old screen is right now...

Sync problem
I've stoped manual sync, edited the name of the single track, and computed the plan. Result: 1 "push".
So better steps to reproduce your problem are needed here, sorry.

Well, to be more precise: I edited the tracks with the route planner, so "Track menu > Route planner > (editing) > Save". Perhaps there is an in-between state when the route planner saves where the tracks is removed from the database?

In a tracks context, the possibility to create embedded waypoints is needed and expected here (by me at least).

I've also always been arguing for adding that to the Track Editor, but Menion doesn't seem to believe in adding waypoints to tracks once they finished recording
Would be happy to be wrong, though...

Do I understand correctly. You want to make a waypoint to a track point. I do not desert for what. Do you have an example?

Well, "Waypoints" tab is part of all tracks. I use them all the time to mark special points and events during a recording. Same could be "general" POIs like "Restaurant", but some like "took off crampons here" are specific to the track. So waypoints make a lot of sense. And sometimes you forget them during recording, but you would like to add them later. While you can do that in the waypoint tab, they now don't have a timestamp anymore, which in cases like my example above are of interest. So adding a waypoint directly to a (timestamped) trackpoint makes a lot of sense. And from reading the threads here, I'm not the only one wishing for this...

But what I think about the track point. I create many track points (per language). To maintain OSM later. After uploading, I delete them all again. But I always have to select and delete each one individually (delete also confirm). Please make all selectable.

Agreed.

In a tracks context, the possibility to create embedded waypoints is needed and expected here (by me at least).

I've also always been arguing for adding that to the Track Editor, but Menion doesn't seem to believe in adding waypoints to tracks once they finished recording
Would be happy to be wrong, though...

[Major sync error!]

Major sync error!

I'm afraid syncing is still not to be trusted. But I can tell you exactly what happened:
As mentioned above, I turned on auto-sync for my phone and tab, let's say device A and B. At the start, both were in sync. Now I edited two tracks on A. I waited a minute or so to let auto-sync do its magic. When I checked again, both tracks were deleted on B! The "Last Update" dialog showed "pullDelete: 2".
And now the kicker: On A, both tracks were still there, but the "Last Update" dialog showed "pushDelete: 2"!!!
Turned off auto-sync on A and B as quickly as possible and restarted Locus on A, just to be sure. And yeah, both tracks were still there.
A "Compute Plan" on A now showed "pullDelete: 2" and "pushDelete: 2". No idea what deletions it wants to push again, but I certainly don't want to pull those wrong deletions.
Anyway, I exported both tracks as GPX and did a manual sync. That worked, but coming back from sync dialog, Locus crashed. After restart, tracks were still there, "Last Update" showed "pullDelete: 2" (but "pushDelete: 0"). Well, tracks were displayed, but clicking them crashes Locus.

Now the next (seemingly better) surprise: Manual sync on B suddenly downloaded the tracks again! Another sync again downloaded both tracks, now finally "Compute plan" showed zeroes everywhere.
Back on A, the next sync also showed "pull: 2" and seemed to download two tracks.

But on both devices, tapping the tracks still crashed Locus reproducibly. So I had no choice but to finally delete the tracks and import the GPX (on A). That worked, tracks could be tapped again. Next sync to B, and finally everything is coming up roses: both tracks are there and clickable, on both devices.

Certainly I'm leaving off auto-sync for now and checking with "Compute Plan" before every sync. But you'll probably admit that that can't be the solution.
The main question obviously is: Why did an edit lead to "pushDelete"?