Messages

Hi guys,
I've just spent on this few hours, so it is funny, that you just discuss it now ...

1. I've found a stupid issue in the current system where the app discarded most of the via-points from the existing route > fixed.

2. I've also improved the whole system so in the next version it will handle "Manual recalculation" settings and it should in case of "Route priority", find the nearest point on the track and create really only detour as small as possible.

[@lor74cas]

@lor74cas
I use it quite a lot to be true. In areas I know, it is nice to simply let the app decide where to go without the need to think too much about it. Anyway, the current system is based on the GraphHopper online service and this does not have an idea about user preferences. This may be improved later in our own solution, but it will really take some time.

Anyway good point > I do not have exact numbers, how much is this feature really used.

@tapio
Speed is included only in case, it is measured by any sensor. In case, it is measured by GPS or mainly computed from coordinates, it is not (and should not) be included.

@Viajero Perdido
weird problem with auto-update. Are you using automatic backup? Does it work? It uses the same system.
And change leaves at 7 days > you click on for example 4 days,, but it still remains in the UI visible as 7 days? Weird.
Anyway 7 days or 8 days, timing is not precise, so a day is delay is not a big problem, but should not happen.

[@balloni55]

@balloni55
#160: fixed & improved, thanks

@Andrew Heard
hmm, maybe after five years > LoRouter based routes will have set Street name for navigation points!

There is no support regards this "Round trip" feature yet . 0 points > app will use current map center, 1 point > use this. it then generates a round trip in direction and closes to the defined total distance. Try it, it is simple .

Anyway thanks for the nice suggestions in the following post. I'll look at it. I also hope, that Radim finds some time and creates a little more robust in-house solution based on LoRouter that should support what I consider more important - a round trip over at least two (or more) points.

Documentation: don't blame me, it is a task for Michal! And as he does not know what to do sooner (80% of time spent on the help desk), it will take some time ... anyway big "FAQ" blog post will be published this week.

@slarti76
thanks for the tests!
Notification about sync, so-called "push notifications" are currently not completely in our control. It is a service from Google that uses "Google Play services" installed in every Google-supported device. So I really hoped, there won't be any troubles to fix ... hmm, your tablet ...

I'll try to play with more devices at once a little later. Currently, I test mainly web & one device.

Switch track <> trackpoints - I'll think about it.

Track editor > added to "Todo"

@Viajero Perdido
"Round trip" feature is again something not complete in our control. It is a feature that offers GraphHopper service and it simply allows from a single defined point, azimuth and expected distance, "generate/suggest" a "round trip", nothing more.

[MapGooglePlay_4.0.2.3_1007_beta]

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

@balloni55
I'll look at it next week and let you know.

[@freischneider]

@freischneider
Hmm long title is not usual so I do not want to complicate it here. I've improved the track (and also point) metadata edit screen. So now, the long title will be clearly visible there. There you may also copy&paste it.

@Christian
"Platinum Eternal Edition"?  .. you may just publish of Locus Map 4 version? Is there any serious problem in current public version?

@luce
hey, ID works, perfect!! And issue fixed. So it will need another version ... thanks.

@slarti76
description: change is a side-effect of the change I made. In case, description will be longer than on 5 lines, it will be cut just to these five lines and the button "more" appears. It has also the big benefit that description in the main view is a simple text field. But with the "more" button, a big internal web browser opens! So in case, you for example copy&paste some description on the web, it will be perfectly working here together with styling, images etc. Same for points now!

And the copy of the description: thanks, fixed for points & tracks.

---

Problems in the second post. Very nice description, thank you very much!
Interesting is that exactly the same steps are done on my device display always on A device "push: 1, pushDelete: 1", which is expected for now. On the second device then "pull: 1, pullDelete: 1". Interesting.
I'll try to fix this now and making edits in the Route planner really as "update" of existing and not delete old and creating new. We will see if it helps.

The crash that appears after edit in the editor is the same as the crash that @luce reported. It Will be fixed, thanks.

@Andrew Heard
crash info is stored in the app and send when app starts next time.

Swiping point/track panel > you mean on the tablets where is attached to the right side right? I know I know ... tablets are still not well supported ...

[Beta version 4.0.2.2]

New Beta version 4.0.2.2 just uploaded to Google Drive.

Important info:
For a few weeks, I test automatic reports of crashes to "bugsnag" service. Seems that after many years and many services I tried, this one finally works as expected. And the useful part for you: "user ID" visible in the "about app" page in the app since 4.0.2.2, should finally be used to search for crashes on your device. So let's give it a try and if the app crashes, just send me this ID instead of creating bug reports by the quite complicated system as before. Thanks!

Thanks guys. I've probably found the error. Will try to publish a new version today (in the worst case tomorrow).

Můžu jen odkázat sem: https://help.locusmap.eu/topic/dark-mode#comment-95136 . Nové Xiaomi bohužel nikdo v týmu nemáme.

[@freischneider]

@freischneider
You wrote that the point screen does not close when swiping down? Can't confirm. Anyone same problem? Btw. does it happen for the screen above the map? Because when you tap on the point in the list of points, the full-screen window is visible and this can't be removed by this gesture.

Crash when tapping a track: log should be really useful here, thanks.

Improvements in the list of waypoints is planned. As you may notice, I firstly try to make perfect the first initial screen. All screens with details are only copies of the old tabs (chart, waypoints, laps). Once the first page will be perfect, we may discuss other sub-pages.

@tapio
thanks. You have a privilege and I've added this task to around top 20 tasks I want to focus on for now .

Waypoint list: useless? Why? Maybe you start to use different icons for track waypoints 

Alignment of text: I see only a problem with the "walking icon". What else is there a problem in this case of very long texts? And suggestions on how to do it better?

"Right arrows": I never had a problem with them, but if you have better idea for an icon with "Show me more", give it to me

Back from trackpoint: as I wrote to slarti76 below. You do not see the "right arrow" icon in the trackpoint detail right next to the track?

@slarti76
Trigger sync when turning auto-sync on: good point, thanks

Track screen
- selectable title? Eh, ble. Just open "edit" when you need to copy it.
- 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.
- customization is the last step, as usually
- crossing lines on the chart. Nice idea. Not sure if doable, I'll look at it
- back from the trackpoint: there already is a visible panel with parent track and the right arrow button takes you back

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.

@luce
Working slide up/down when working with the chart: I've noticed this as well. it will be an interesting problem.

Full-screen chart: ah, thanks. I would like to convert this old chart system to the new one (used on the first new track screen page). Uff, big task ...

@Andrew Heard
- dark search text in settings > I know. Some system problem I'm still unable to solve :/.
- return to the root of settings after screen on/off. This is on the second side my own problem that requires a more complicated solution and I still do not consider this as a big problem, so ... thanks for understanding.

@sbouju
May you please write your question in detail? Unfortunately, it's not clear at least to me, thanks.

Zdravím též,
zkus prosím novější verzi 4.0.2, snad tam už trasy pojedou korektně!
Pokud se trasa vytvořená na webu v aplikaci neobjeví, tak jen na webu uprav např. její jméno aby se označila jako nová.

Chybějící fce na webu: no rok práce, za to se tolik nestihne. Start nové verze se nám snad celkem podařil, takže teď budou funkce jen přibývat .

A odinstalace by neměl být problém. Pokud Free verze data vidí, používají tedy slopečný adresář "Locus" v rootu interní paměti a pak by neměl být problém.

[Beta version]

So the core sync problem fixed, perfect, thanks guys!

Beta version
damn, this is really complicated task now  . Andrew, I probably see your crash in auto reporting system. Seems two users already have this problem. Reason? You probably set the bottom panel to full auto-hide and 4.0.2 does not know this option = crash  .

Solution? New Beta!! 

Link in the first post or here: http://bit.ly/lmVersionsTest

@tapio
ah vacation. I've almost forget.
Is there anywhere existing topic on the help desk? Can find any. I would like to add it to my to-do list.

@Hennes
interesting problem. May you please do just a tiny modification on the web, like change any letter in the track name? Because it is possible that because of the bug in 4.0.1, the track is marked as correctly synced, but it isn't. Sorry for this.

[@balloni55]

Thanks for the feedbacks regards the new track screen. I won't comment this yet, but seems you are +- Ok with this change, fine .

@balloni55
Placing magnifier and zoom lock as you wrote is of course doable. Any idea how to solve this? Btw. is it really a problem?

@Andrew Heard
- hidden "Map-screen content" is no option for me, sorry. This is the correct button that has to be always available. Many features are accessible only from this panel (and will come more probably).

@luce
Automatic sync has to be enabled for sharing a track over Url, it is necessary requirement. I'll check what you wrote, thanks.

Crash when opening tracks, hmm. I've of course did not notice such a problem. Will have to open more tracks probably .

---

New version 4.0.2 released at the night. Should mainly fix troubles with the sync of tracks that some users suffer with.

[@balloni55]

@balloni55, @Diddi
really, still crashes? Damn!

@lor74cas
Mess, I know  . Live tracking will be integrated into web.locusmap.app, so this will be solved. Anyway, the rest ... it looks like we will need some guy skilled with PHP who will take care of it. We tried at unite design with existing webs some time ago at least a little bit ...

Because I'm no longer alone on these tasks, as I see in our Who we are page (finally visible our faces, nice right?  ), it is best to job for @Jan Čapek . Jan, any comment here?

It was enabled in the Beta version only because I was not yet sure about this solution > I believed I find some better. But not yet and by accident, it was not enabled in the production version. Will be fixed in today's new version.

Michal discovered this yesterday as well. Together with "magnifier", these items were available as a button to function panel, but only in Beta. I've forget to enable this in the final version, sorry. So in the next version ...