Locus Map - forum

Development => Versions => Topic started by: menion on August 09, 2017, 18:25:00

Title: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 09, 2017, 18:25:00
Important links
- blog post (http://www.locusmap.eu/news-version-3-25-0) about major version
- list of news (http://help.locusmap.eu/announcement/version-3-25-9-8-2017) of public versions

Versions
7. 9. 2017 - Locus 3.25.5.1 - beta
5. 9. 2017 - Locus 3.25.4/5 - bug-fix
31. 8. 2017 - Locus 3.25.3 - bug-fix
28. 8. 2017 - Locus 3.25.2.3 - beta
25. 8. 2017 - Locus 3.25.2.2 - beta
21. 8. 2017 - Locus 3.25.2 - bug-fix
15. 8. 2017 - Locus 3.25.1.3 - beta
12. 8. 2017 - Locus 3.25.1.2 - beta
11. 8. 2017 - Locus 3.25.1.1 - beta
10. 8. 2017 - Locus 3.25.1 - bug-fix
9. 8. 2017 - Locus 3.25.0
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on August 10, 2017, 21:05:23
Hello menion
after update to V 3.25.1
color of my geocaching icons change :-[ if i select another preset, it´s not allways, but very often.
Only restart of locus solve the color problem of the icons
https://www.dropbox.com/s/7tbx9iulfy4qkp9/Icon%20color.mp4?dl=0
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 10, 2017, 21:46:48
Hi balloni,
this is really interesting. Really can't understand what has preset in common with your custom icons ..

Firstly please check if you have disabled all mapItems. If yes and it still happen, may I get your custom icons for test and rather also profile file ( Locus/data/profiles ) , just for sure? Thank you.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: c.s.g. on August 10, 2017, 21:56:55
Hello,

after update to 3.25.1 I do not find the dialog to change themes of vectormaps in "Karten" window "OFFLINE" tab.
In earlier versions there was a menuitem "Detail" when I click on the 3 points after the name of the vectormap where I was able to change the theme. Now there is a new menuitem "Information & Sprache" where I can change the language of the vectormap but not the theme anymore.

I am using Locus Pro on a Samsung Note 4 running Android 6.0.1 Stock ROM.

c.s.g.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Jere on August 10, 2017, 21:58:20
- list of news: list of news (http://help.locusmap.eu/announcement/version-3-25-0-10-8-2017) ( tomorrow)

...link still doesn't work
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 10, 2017, 22:37:52
@c.s.g. yes, this is correct. Based on statistics I received, this button was used only in 6% of all theme changes, which I consider as too low. So please use any of main two methods > left side panel or functions panel. Thanks

@Jere: thanks, fixed correct url
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on August 11, 2017, 03:36:53
3.25.1 presets > set functions panels > set current content (button) - nothing happens.

also still have the same BIG problem already discussed but @menion could not reproduce where function panel sets of each preset get confused, corrupted. Lost all my 3.24 function panel buttons. So deleted all my presets, started completely from scratch. But still same issues with the correct, or any! function panel buttons. Just wasted the last hour setting all buttons up again for each preset, and now lost. Are you sure you tried with auto-hide top and left panels? I will just have to remove this new feature from each preset for now until sorted as has caused lots of trouble.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: c.s.g. on August 11, 2017, 09:09:36
@menion: Thanks for the info ....

BTW I am using the geocaching icons of balloni55 too. But I have no problems like balloni55 with them. Maybe it is because I do not use any presets so far and therefore have no need to change between these presets.

But if I remember it right, these icons are rather "big". I think they have a size of 100x100 pixels. Maybe this causes the trouble because the recomended icon size is 48x48 pixels if I remeber this correct too.

c.s.g.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 11, 2017, 10:23:55
@Andrew Heard : hmm sorry to hear you still have issues with this function. I just tried to play around 15 minutes with it and still no problem, damn.
Just to make it clear to me ... you have an issue just with playing with latest 3.25.1 version, no switching to some older beta or Pro version, just latest update right?
You tried to describe me your issue already twice, like here http://forum.locusmap.eu/index.php?topic=5720.msg48261#msg48261 , but it always looks to me like some problem caused by changing of older Locus Map Pro ( that not yet supported function panels so this option was lost ) and latest Beta.

@c. s. g: I was also using some custom packs for geocaching icons during testing of changes I made in rendering points ( hope you notice speed improvements when more caches is visible at once ) and also have no such issue of course. It looks like icons are colored by some other color, which may happen only in case, loaded KML file (over mapItems) has defined style with custom color and this color is for any reason incorrectly reset. But change of preset should cause no change here, really interesting.

Maybe try smallest possible "preset" and test which option in preset cause this. Thanks!
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: JoxM on August 11, 2017, 22:49:18
Hi,
Since some time (not from this version on) I have figured out some strange behaviour of my installation.
1. Links in geocache listings doesn't work. They start, then some flickering of the screen and then listing is shown again. Sometimes it works after trying several times. (pro and beta)
2. When I try to update the logs of geocaching the updated logs are not shown directly as before. I have to get out of the listing and reopen it again and then I see the updated logs. This is in pro version. In beta it works like before.
3. Same issue as #2 but with the cache solver app. When I add a waypoint in this app normally this waypoint was directly displayed when returning to locus. Now I have to leave the listing and after re-entering the waypoint is shown. Only pro, beta works.

I already checked both installed versions, but all the settings are absolutely equal. Perhaps something in config file?

Greetings JoxM
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on August 12, 2017, 00:46:30
Hi @menion. Regards presets, I am discussing experience from 3.24.3 direct to 3.25.1. So yes, 3.24.3 had no preset function panels. So you would think I was "starting from scratch" in 3.25.1. For each of my presets I emailed function panels. All seemed ok. Then I modified one preset to have different set of buttons, and nothing was working. I tried disabling function panels in all presets, and just created 2 completely new presets All On/ All Off. I can't "set current buttons" but as I said this doesn't work at all. Maybe that is easiest function to debug? Special build or log file?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on August 12, 2017, 13:19:40
Hello menion
Quote
Firstly please check if you have disabled all mapItems
i have had no enabeled mapitem
Quote
color of my geocaching icons change
sorry, since two days i cant reproduce this fault
I am at a loss, so we´ll wait ;)

since  V 3.25. there is always a grey round sign (GPS ??) with changing number 1...8 at this position
on my SGS2 with only GPS receicer and on my Moto G3 with GPS and Glonass receiver
(https://s21.postimg.org/nb9pw6fw3/grau1.jpg) (https://postimg.org/image/nb9pw6fw3/)

EDIT:
this grey round sign is also visible with external BT receiver receiving Galileoand BeiDou
(https://s17.postimg.org/khcvg23ob/grau.jpg) (https://postimg.org/image/khcvg23ob/)




Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: c.s.g. on August 12, 2017, 14:32:01
Hi,

I found a little "bug" in the new import windows for geocaches / waypoints of Locus Pro 3.25.1.

I. e. I have a gpx file with 5878 geocaches and several child waypoints for some of the geocaches. When importing this gpx file, the progress of the count Punkte is correct and shows 5878 Punkte at the end but the progressbar below this label is lagging behind the real import progress. When all 5878 geocaches are imported the progressbar shows only 61% of total progress.

I suppose the max value of the progressbar includes the count of all waypoints, i. e. geocaches and child waypoints of the geocaches, the step value of the progressbar respects only the count of the geocaches without correspondig child waypoints.

c.s.g.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: joeloc on August 12, 2017, 19:08:15
I realize you're not the king of user interfaces... :), but the latest locus pro is utterly messed up for me. Somehow, the tiny map in point window gets besides the name instead of below or some such. Doesn't happen all the time, but at least in 50% of all cases. See attached pic.

Oh also... the search window is somehow too wide now... so the UI is invisible left and right.

All in all, new pro is reasonably bugged regarding UI. I wish I had backed up the old one :)

Note 4, Standard Marshmallow, no dpi hacks.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 12, 2017, 20:52:51
@Andrew Heard: I hoped there will be someone who confirm this problem as well and maybe bring some light on it, but you are still alone ... weird. I'll probably prepare some test version, but do not exactly know what check and what not, damn complicated ...

@balloni55
: oki, thanks :).
Small grey circle with number ... in versions before, on this place was satellites with unknown location, but in their shapes and colors, so mess ... I've at least placed them into grey circle with number ... so it's number of sats with unknown location on sky

@c.s.g
. : thanks, clear description, I'll check it

@joeloc: more and more I think, I'm king of UI between developers ;). Interesting what I see on your screenshot. During years, I never saw about problems with landscape&portrait in incorrect moment ... and during last weeks, twice. You and this guys here (http://forum.locusmap.eu/index.php?topic=5833.0) . So this is not a problem in design, but in fact that Locus try to use layout for landscape in your portrait mode!
There have to be something in common ... really nothing changed that may affect this? What about non-default language selected in Locus? When you rotate screen, it fix this?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: joeloc on August 12, 2017, 21:01:11
Landscape vs Portrait is correct... I also have this in many other places in Locus... like live tracking entry list eg. Rotating fixed it temporarily, but it *beeps*" up soon again after.

This only started like a week ago. Never had this before.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: joeloc on August 12, 2017, 22:52:32
Hmm... Locus was set to English, system was set to German. Now I set Locus to system default, but it still comes up in English?!

The landscape problem seems to have disappeared for now though :)
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: passosk58 on August 13, 2017, 02:00:53
I chose screen allways on and unlock screen disabled. But allway shutdown the screen when i start again the screen is allways blocked..doesnt work this feature..

I wave Redmi4prime with miui8

Enviado do meu Redmi+4 através de Tapatalk
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 13, 2017, 06:21:57
@joeloc: thanks, I though it might be because of this. Setup of locale on Android other then default system is always a hack and seems it has some side effects. Default locale should help ( if not, I've improved it so it will definitely help in next version ).
Complicated task ... I need to test it on own devices with hope, some will have same problems. Needs some to perform some tests ...

@passosk58: probably known problem ... please check this Dmitry's discovery: http://help.locusmap.eu/topic/the-disable-screen-lock-setting-stopped-working-recently#comment-43392
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: joeloc on August 13, 2017, 07:00:26
Locus decided to be in German now... and the UI is messed up horizontally again. So maybe not related.

Many places are messed up... plenty of the lists are close to unusable because I can only see 3 or 4 chars of an entry.

This happens by itself after a few minutes/seconds, even without me ever rotating the phone horizontally. It never goes back to vertical layout, even when I rotate the phone around like a mad man.

Help!
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 13, 2017, 08:49:57
There have to be something special on your device! There is many users with Note 4 and such huge problem will definitely cause a lot bigger response at least in comments on Google Play.

May I offer for now at least previous stable 3.24.3 (https://nas.asamm.com/share.cgi?ssid=0KJGXIj) version?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Tom on August 13, 2017, 14:22:27
Hi Menion,

I guess this issue is related to this topic http://forum.locusmap.eu/index.php?topic=5833.new#new (http://forum.locusmap.eu/index.php?topic=5833.new#new). At least for the maps manager the problem is 100% reproducible on my device (Samsung A3 2017).

Regards
Thomas
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: alezy on August 13, 2017, 15:10:17
I have problem like @joeloc, with language switching, and I have MIUI too. For me language switches after I  closing Locus by system.
In beta I have small problem: open point details -> share -> Other map apps and it says "Application for selected feature is missing in your device", but Pro shows many apps.
Two small suggestions:
1. in Point details -> Navigation I see some application, that I'm not using, but my favorite applications is under "Navigation maps" menu, so can you dynamically to show in that list some of last used applications, rather than predefined list?
2. In Point menu I have "Navigate to", but can you add another item like "Navigate to via last selected navigation application", like Waze? It is useful because I'm using Locus as great POI manager and in many city trips it is better to use external navigation that takes traffic jams into account, instead of BRouter/MapQuest/GraphHopper, Yes, Locus is offroad application, but to "offroad" I must havigate  thorough cities
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: joeloc on August 15, 2017, 14:06:36
There have to be something special on your device! There is many users with Note 4 and such huge problem will definitely cause a lot bigger response at least in comments on Google Play.

May I offer for now at least previous stable 3.24.3 (https://nas.asamm.com/share.cgi?ssid=0KJGXIj) version?
that one doesn't mess up the UI, but loses gps once every 5 minutes and never re-enables it until I do it manually.

.. guess I must abort the trip...
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Haggi on August 15, 2017, 14:15:52
that one doesn't mess up the UI, but loses gps once every 5 minutes and never re-enables it until I do it manually.

I had to use this app for same reason a couple of years ago.. https://play.google.com/store/apps/details?id=com.webmajstr.gpson
Problems was not related to Locus but different app.
It forces GPS active..
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: joeloc on August 15, 2017, 16:22:06
"Downgrading" Locus to a previous version has always been a bit messy for me. I have to uninstall the current Locus first, because Android 6 won't let me put an apk on top of a newer version. Then I can restore prefs from a backup, then the weirdness starts: The prefs "seem" correct, ie all the values in the settings windows are fine. Yet Locus will still use the defaults from the new apk installation . I have to enter each settings window manually and sort of click each settings item (not changing it) to make Locus actually use the restored Settings.

Just mentioning... not a major issue. Major issue is the horizontal UI I guess !:)
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 15, 2017, 18:37:17
Quite complicated task because of missing device with this problem and clear tested working system by any other developer.

Anyway after afternoon fight, I modified Locus little bit about this problem and just now published new Beta version 3.25.1.3 , so please try it and let me know.

If custom selected language won't work, set "default". In next Beta, this option now should make absolutely no modifications to background app/system settings.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on August 15, 2017, 21:43:11
V 3.25.1.3
all icons of POI´s inside point tab and folders are displayed as blue dot
in POI detail and on map icons are displayed well
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 15, 2017, 21:49:32
Kill me! I did some tests on database performance and forget to revert this part. Sorry .... new version is in preparation ... thanks balloni!!
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on August 15, 2017, 21:56:00
Quote
Kill me!
certainly not ;)
we need you for further tasks :-*
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 15, 2017, 22:23:03
Glad to hear it ... anyway stupid mistake.

Beta is out and I'm going to sleep. Wish you nice next two days and please excuse me ... small two day bike trip with my brother-in-law, so I won't be available. Route planner and absolute slope coloring and many others expect deep testing ;). Good night
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Viajero Perdido on August 16, 2017, 06:36:40
I just noticed something odd, and since you guys are talking about language issues, I'll mention it.

I downloaded the Vietnam map from the store last night, and I'm seeing a lot of POIs prefixed with "en" on the map.  Investigating, it seems that any POI that has a "name:en" but not "name" tags has the "en" part rendered on the map, eg "en Banh Xeo" corresponding to http://www.openstreetmap.org/node/4504245791.  OSM history tells me everything is normal at that end.

Beta does this too.

BTW, wouldn't it be more useful for the hover text to say "Banh Xeo" instead of "Restaurant"?  I already know it's a restaurant from the icon.

Thanks.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: lor74cas on August 16, 2017, 07:34:43
Hello,
in Locus Pro when I open the points end tracks window and I chose tracks or points form, the next time locus remembers the form I selected the previous time. In the beta this doesn't happen, it's always fixed to points.



Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on August 16, 2017, 19:31:04
@ lor74cas
Quote
In the beta this doesn't happen, it's always fixed to points
have you tried V 3.25.1.5 ?
for me it open last state
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: lor74cas on August 16, 2017, 19:58:21
@ lor74cas
Quote
In the beta this doesn't happen, it's always fixed to points
have you tried V 3.25.1.5 ?
for me it open last state
Pro 3.25.1
Beta 3.25.1.5

Inviato dal mio SM-G800F utilizzando Tapatalk
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: joeloc on August 16, 2017, 20:45:15
@menion, my google account somehow lost beta versions access... can't test the latest fix. But the last stable that you linked here for download does NOT have the Horizontal/Vertical problem. Everything works normally. So it must be something you changed between then and now.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: c.s.g. on August 16, 2017, 21:42:16
Hi,

I have a problem using the adress search with the germany_north map of 22.07.2017 with Locus Pro 3.25.1 on my Samsung Galaxy Note 4, Android 6.0.1 Stock ROM.

I. e. when i search for Wesselburen via "Suche nach Adresse (offline)" the blue icon with the envelope is shown at the center of Wesselburen but the red position cross is about 1 to 2 km more south placed. The offline map is centered on the screen to the red position cross!?

Doing the same search via "GeoNames und GNS" the blue icon with the magnifying lens and the red position cross are shown at the same position on the map in screen center.

Or if it have to be a bigger town ;), try Hamburg. There the offset is even bigger using "Suche nach Adresse (offline)" but works as expected using "GeoNames und GNS".

So it looks like this is a "Locus problem" rather than be a "map problem".

And: Neither the centering button nor the rotating button is active.

c.s.g.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on August 17, 2017, 06:17:04
@menion can one of the blue colors be made more different? a waste of space at present as they look very similar:
(https://s2.postimg.org/o54g4uiqt/2017-08-17_14_14_22-.png) (https://postimg.org/image/o54g4uiqt/)
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on August 17, 2017, 07:16:46
@Andrew Heard : hmm sorry to hear you still have issues with this function. I just tried to play around 15 minutes with it and still no problem, damn.
Just to make it clear to me ... you have an issue just with playing with latest 3.25.1 version, no switching to some older beta or Pro version, just latest update right?
You tried to describe me your issue already twice, like here http://forum.locusmap.eu/index.php?topic=5720.msg48261#msg48261 , but it always looks to me like some problem caused by changing of older Locus Map Pro ( that not yet supported function panels so this option was lost ) and latest Beta.
@menion - more testing of preset function panels only using 3.25.1 Pro...

So I delete both presets again. This time I add 1st preset again and behavior is slightly different...
(https://s27.postimg.org/kszvqz07j/2017-08-17_15_25_22-.png) (https://postimg.org/image/kszvqz07j/)
Have you tested with so many RHS buttons?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: slarti76 on August 17, 2017, 08:37:33
@menion can one of the blue colors be made more different? a waste of space at present as they look very similar:
(https://s2.postimg.org/o54g4uiqt/2017-08-17_14_14_22-.png) (https://postimg.org/image/o54g4uiqt/)
I think they should be kept, but there's definitely space for a lighter blue, like #7777FF would be nice. And while we're at it, a dark gray like #777777 wouldn't hurt either, as would a real dark green like #005500.
Menion, I know that these colors have a very systematic origin (you sent me the PDF), but looking at them in practice, I feel there's some missing that are more likely to be used in "real life".
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: slarti76 on August 17, 2017, 09:35:43
I think they should be kept, but there's definitely space for a lighter blue, like #7777FF would be nice. And while we're at it, a dark gray like #777777 wouldn't hurt either, as would a real dark green like #005500.
Menion, I know that these colors have a very systematic origin (you sent me the PDF), but looking at them in practice, I feel there's some missing that are more likely to be used in "real life".
PS: Being able to define personal custom colors would be the best, of course. Could be displayed as third section after "ZX Spectrum" and "Secondary Colors".
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Viajero Perdido on August 17, 2017, 18:19:14
A couple of minor glitches in 3.25.1 (non-beta):

When I imported 6 PQs at once (from Geocaching Tools), the progress dialog said "files: 7".  Happened on both my devices, and I carefully counted my checkboxes the second time.  Six.

When I imported a single PQ from the bottom of a long list, the Line Tools or Middle Point dialog popped up unexpectedly.  Either my tap on the PQ checkbox or the tap on the button to begin importing was also received by the Geocaching Tools panel behind it.  Right around the bottom of the screen.  (I'm not using full-screen mode.)

But the imports seem to be working fine, so no big deal.

I'm going offline soon, so won't be able to reply to anything.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: voldapet on August 18, 2017, 10:07:27
Investigating, it seems that any POI that has a "name:en" but not "name" tags has the "en" part rendered on the map, eg "en Banh Xeo" corresponding to http://www.openstreetmap.org/node/4504245791. 
Thank you - Fixed

Locus by default shows the name of the poi  - try for example this one https://www.openstreetmap.org/node/3575188505
The node "Banh Xeo" is little bit complicated  because there is defined only the "en:name" not the default locale name. Locus does not show the name because the locale name is missing and as fallback mechanism shows at least the type of point. We'll try to improve the POI DB to handle also this situation.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Viajero Perdido on August 18, 2017, 17:04:38
...as fallback mechanism shows at least the type of point.
Ah, a fallback mechanism, got it.  When I wrote that, I thought it was showing "Restaurant" for all such POIs, but I see now it's only doing that for "problem" POIs like the one I pointed out.  That's not so bad.

But Hanoi is full of those problem POIs, if you need something for testing.

Thanks for the quick fix on "en".
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 18, 2017, 19:11:28
@lor74cas: also can't confirm. Please check you really use correct button to open data manager .. there are three icons ( data manager, data manage > points, data manager > tracks)

@joeloc: Beta testing: http://docs.locusmap.eu/doku.php?id=manual:about:free_beta_testing

@c.s.g: problem with centering on found location will be fixed in next version, thanks

@Andrew Heard , @slarti76 : guys, you wants to modify palette of ZX Spectrum?  :o ;D . Andrew, thanks for precise step-by-step description of function panel problem, will try it tomorrow

@Viajero Perdido: problems with incorrect number of files will be solved in next version. Some popup of unwanted screen is interesting. Hard to fix without steps to simulate. Does it happen again and again?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: lor74cas on August 18, 2017, 20:27:05
@lor74cas: also can't confirm. Please check you really use correct button to open data manager .. there are three icons ( data manager, data manage > points, data manager > tracks)

@joeloc: Beta testing: http://docs.locusmap.eu/doku.php?id=manual:about:free_beta_testing

@c.s.g: problem with centering on found location will be fixed in next version, thanks

@Andrew Heard , @slarti76 : guys, you wants to modify palette of ZX Spectrum?  :o ;D . Andrew, thanks for precise step-by-step description of function panel problem, will try it tomorrow

@Viajero Perdido: problems with incorrect number of files will be solved in next version. Some popup of unwanted screen is interesting. Hard to fix without steps to simulate. Does it happen again and again?
Found it !
The shortcut in the panel was set up one to points in a version and one to data manager. The window is the same but obviously in the first case it opens always points form.
My fault, in one of the latest updates of beta I lost my preferences and I did set up the wrong one.
But why in the function panel we can find both points and tracks icons instead of only a data manager icon?

Inviato dal mio SM-G800F utilizzando Tapatalk

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: voldapet on August 18, 2017, 21:34:59
@Viajero Perdido: problems with Restaurant vs Name in POI label will be solved in next version of LoMaps. I generated for you custom Vietnam osm.db file. You can download it at: https://nas.asamm.com/share.cgi?ssid=0JSywGw

(https://s11.postimg.org/hf4utd1gv/lomaps_vietnam_poi_label.png) (https://postimg.org/image/hf4utd1gv/)
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: 0709 on August 20, 2017, 14:02:47
New style track edit function.
- Buttons need to be placed further apart.
(https://www.imgdumper.nl/uploads9/59997a30f2603/59997a30dcf1c-Petite.png)
Prefer old style edit toolbar
+ Button distance ok
+ Nicely lined up in a single toolbar.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on August 21, 2017, 00:37:52
Locus 3.25.1.5 tap on-screen existing track > Route Planner > consistent crash/ auto-restart -
see video (https://www.youtube.com/watch?v=GEIeHF447xA).
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on August 21, 2017, 00:40:49
New style track edit function.
- Buttons need to be placed further apart.
Prefer old style edit toolbar
+ Button distance ok
+ Nicely lined up in a single toolbar.
The triangle inside each Modify Track circle button could be made larger. The equivalent +/- inside each Route Planner circle button are now much better.
(https://s3.postimg.org/z27cdqoyn/2017-08-21_08_39_09-_APP_-_version_3.25._9.png) (https://postimages.org/)
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 21, 2017, 11:21:42
@lor74cas: fine.
Both icons .. "data manager" is confusing for a new users so we added "points" and "tracks" options that are by default in main menu. Anyway data manager remained there to allow one click access to last used tab in data manager ( it was more important before when there were also third tab with "map items" ).

@0709: it looks you are using it on tablet or on device in landscape mode right? For this, is layout not yet perfectly optimized.

@Andrew Heard: thanks for a video. Unfortunately because I do not have same error, video does not help here, only a log (probably). Anyway I made a lot of changes in route planner since latest Beta, so please wait on next version, thanks.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: 0709 on August 21, 2017, 12:27:30
Tab 4 portrait.  No remark about modern design. Just those buttons that are frequently tapped at operations need some extra space.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: JoxM on August 22, 2017, 20:15:04
Hi again,
Does anybody has the same issues like me explained in post #10?
I already reinstalled Locus pro, but no changes. I use exactly the same config (backup from beta and installed in pro).
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on August 22, 2017, 20:34:29
Quote
Does anybody has the same issues like me explained in post #10?
i can confirm your issue nr.2, to see new loggs i have to reopen the listing after i run update cache
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on August 23, 2017, 06:47:28
@Andrew Heard thanks for precise step-by-step description of function panel problem, will try it tomorrow
@menion - I did some more testing of preset function panels only using 3.25.2 Pro. Did you get any time to test? You'd hadn't said whether you tested with large number of panel buttons on RHS. In the past I've had 15. I had a theory maybe bug is related to large #. I removed 8, so now all RHS buttons visible. It seemed to work for a while. But then some presets went from 5|7 to 5|0 again. Always the top panel buttons remain stable. It never takes long before the # buttons goes wrong. Just switch between presets a few times, then edit to check #|#. Add/ remove a few buttons from a preset/panel. Thank goodness backup/ restore works although I would like to use this new feature.

PS. I cleared Pro & Beta data caches (settings > Apps > app > Clear cache. Same problems.

I was going to completely uninstall Locus & install from scratch but for some reason the Uninstall button is disabled. Any suggestion?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Christian on August 23, 2017, 16:42:26
3.25.2
Tap zip-file in file manager containing gpx -> open with Locus Pro -> select folder -> create new folder -> name the new folder.
The created folder can not be choosen within dialog for track import.
:(
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on August 24, 2017, 00:42:11
@Menion - I note there is a new version of the help desk. Inline picture uploading & other UI is slightly different. A few times already the link button has not worked. I select text, click Link button, paste in the URL, press Enter key ==> the selected text has been deleted. Very annoying. Can this be reported to the help desk supplier?

Another example of issues with new help desk: I start writing a comment/ reply. If I now click on any links of previous user, say to view image link or download an attachment, all my comment text is deleted. Even more annoying. This didn't happen with previous version. I can workaround by right-clicking on links.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 25, 2017, 10:57:37
@JoxM: ah I've forget to test it ... you wrote in Beta it's ok? In latest 3.25.2 is still this problem?

@Andrew Heard: testing your exact steps and no problem. Also no-one other reported same problem. Weird, mainly because it cannot be based on any Android version etc.
Please this (https://nas.asamm.com/share.cgi?ssid=0zmtETh) test version, simulate problem and close app. In Locus/logs directory should be some text logs, so send me them, thanks!

@Christian: thanks confirmed, I'll look at it
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: JoxM on August 25, 2017, 11:20:10
@menion: yes, in Beta it's ok. No changes since last update.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 25, 2017, 13:42:22
After quite a lot of testing, I'm finally starting to be satisfied with new Route planner.
Enjoy it, new Beta 3.25.2.2 just uploading.

Btw, what a few of you who had troubles with UI, is it fixed? Mainly @joeloc ... you usually complain, but rarely tell me if it's fixed and working as expected.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on August 25, 2017, 16:37:15
V 3.25.2.2
you wrote: add nogo area > BRouter 1.5+
where can i download it??
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Viajero Perdido on August 25, 2017, 20:12:36
@Viajero Perdido: problems with incorrect number of files will be solved in next version. Some popup of unwanted screen is interesting. Hard to fix without steps to simulate. Does it happen again and again?
Hi Menion.  I can duplicate it SOMETIMES, though it's not annoying.  You need a long list of PQs ready for import.  Here's what I did:
On my medium-resolution phone, I went into Geocaching Tools; on my phone "Middle Point" is the last thing visible; the explanatory sentence was not.  (I'm not using full-screen mode.)  I tapped Load Pocket Queries, and that showed a list longer than the screen.  I scrolled right to the bottom, and selected the single checkbox at the bottom.  Tapped Import.  That brought up the screen for that PQ.  Tapped Cancel.  The Line Tools or Middle Point dialog (can't remember now which one, sorry) was showing; I'd briefly seen it pop up and then get covered by the PQ dialog.

Today I was only able to duplicate this once, sorry.

I hate bug reports that can't be duplicated.  (I've been in your shoes...)
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Viajero Perdido on August 25, 2017, 20:14:30
I generated for you custom Vietnam osm.db file. You can download it at: https://nas.asamm.com/share.cgi?ssid=0JSywGw

(https://s11.postimg.org/hf4utd1gv/lomaps_vietnam_poi_label.png) (https://postimg.org/image/hf4utd1gv/)
This is far beyond the call of duty.  Thank you!!!

PS, both fixes work quite well.  (I can't believe how fast you guys work!)
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 25, 2017, 22:04:07
@balloni55 : you have to push Arndt little bit :). I have from him some test version for testing of this feature only ...

@Viajero: hmm oki, I'll try to simulate it, thanks.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on August 26, 2017, 01:46:02
@Andrew Heard: testing your exact steps and no problem. Also no-one other reported same problem. Weird, mainly because it cannot be based on any Android version etc.
Please this (https://nas.asamm.com/share.cgi?ssid=0zmtETh) test version, simulate problem and close app. In Locus/logs directory should be some text logs, so send me them, thanks!
@menion - preset function panel bug reproduced
4 files in Locus/logs 26/8/2017 0924..0936, I note lots of exceptions, I hope you can figure out the problem.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on August 26, 2017, 02:08:21
3.25.2.1 (your preset logging version)
1) Tracks > select existing track > Route planner > "Unfortunately Locus Map has stopped"
2) Route planner (new route), BRouter - add some manual points, BRouter adds blue navigation waypoints, tap on blue point to move, displays the instruction (eg. left) but no option to move/ delete this point? But for other blue points > tap > name > tap arrow > Edit location. Inconsistent - some blue points can be edited, others not.
Should I keep this logging version or upgrade to 3.25.2.2? Maybe above 1 & 2 are fixed in latest beta?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 26, 2017, 10:47:12
@Andrew Heard: aaaa got it. Complicated issue caused by bigger number of external applications added to functions panel and often change of content. Fixed (hope), thanks!

Version x.1 and x.2 are almost identical except writing to file, so feel free to update to x.2 without worry.

Your second post:
1) this will need a crash log as I'm again not able to simulate it. Probably problem of some specific track only?
2) Currently it is possible to modify only core points that define shape of track (small red, green, blue dots). Blue dots you talk about, are probably navigation commands that are just simplified for drawing in route planner, but agree it looks similar to defined "via points". This is anyway complicated task that is somewhere between route planner and track editor ... will have to think about it more. Thanks
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on August 27, 2017, 03:52:36
@Andrew Heard: aaaa got it. Complicated issue caused by bigger number of external applications added to functions panel and often change of content. Fixed (hope), thanks!
@menion - excellent

Your second post:
1) this will need a crash log as I'm again not able to simulate it. Probably problem of some specific track only?
I've tried 4 different tracks. All quite different, short/ long/ circular/ linear/ different maps. All same problem. Have generated a log and emailing now. Huge file.

2) Currently it is possible to modify only core points that define shape of track (small red, green, blue dots). Blue dots you talk about, are probably navigation commands that are just simplified for drawing in route planner, but agree it looks similar to defined "via points". This is anyway complicated task that is somewhere between route planner and track editor ... will have to think about it more. Thanks
blue dots - correct - BRouter navigation commands; confusing from a UX point of view; pity a way of providing unified route planning/ track editing UX is not being considered.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 27, 2017, 07:56:20
Thanks Andrew, log helped. You use app in different way and because of this i wasn't able to simulate it. Workaround ... display track on the map and then start route planner, it helps. Will be anyway in next version, thanks!
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on August 27, 2017, 09:45:02
OK, that method doesn't crash. However existing circular (out & back) track > Route planner > results in very short loop track of few 10's of metres of recalculated route from start to end (at nearly same point) because there are no waypoints in example tracks. Is this your intention? Of course, if existing track is point-to-point (not a loop) then this issue doesn't occur.

For Route planner > menu > Add new point > Select location: why does this window not have "Select on map"? When a green point (eg. start or end point) is tapped > Edit > "Select on map" is an option. So why the difference? How do you add a new point at an arbitrary location by choosing on the map?

Also when a point is added, choice is add to start/ end/ route, but what if there are two waypoints and you want to add the point in between them? Where is the point actually added when "add to route" is selected? Wouldn't it be better you can tap any place on the existing track, and then chose to "add new point"?

I love the new bottom statistics panel, and the elevation graph which can be dragged up.

When using the Route planner if I change the compute engine, why I don't see the route recalculated?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 27, 2017, 12:01:24
OK, that method doesn't crash. However existing circular (out & back) track > Route planner > results in very short loop track of few 10's of metres of recalculated route from start to end (at nearly same point) because there are no waypoints in example tracks. Is this your intention? Of course, if existing track is point-to-point (not a loop) then this issue doesn't occur.
Well this is complicated. Such very short route happen right after recalculation, right? It's because definition points are only at start and end.
Try to create such route with latest Locus Map version! Definition of route (green/blue) dots should be preserved now!! so original track should be 1:1 restored in route planner and this problem does not happen (in case you used also some middle point to define this "round trip"). Anyway with old track or track imported from file, this happen.

For Route planner > menu > Add new point > Select location: why does this window not have "Select on map"? When a green point (eg. start or end point) is tapped > Edit > "Select on map" is an option. So why the difference? How do you add a new point at an arbitrary location by choosing on the map?
Ah thanks, should not be in context menu of point as well.
How to? Simply center map center cross to required place and tap on bottom left "+" button. Or even better, long click on wanted place which gives you even three choices where to place new point as you mention below.

Also when a point is added, choice is add to start/ end/ route, but what if there are two waypoints and you want to add the point in between them? Where is the point actually added when "add to route" is selected? Wouldn't it be better you can tap any place on the existing track, and then chose to "add new point"?
To add point in middle ... fastest is long click on map on place you wants to add and choose "Add to route". Locus tries to find best possible place in middle of track or in worst case add point at start or end of route.

When using the Route planner if I change the compute engine, why I don't see the route recalculated?
And why it should? System is same as before ... defined engine is applied on new added or changed track parts. There is still option that you wants part compute by one engine and second part by different. Locus gives this option ...
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 28, 2017, 20:00:41
New Beta version 3.25.22.3

What needs mainly test, it work in new Route planner screen. Hope you will find it useful as is now :).
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on August 29, 2017, 02:03:04
Testing with 3.25.3.3
This beta expires in only 2 days! Not much time to test.

So far preset function panels are working reliably! Well done.

What is use-case for dashboard in track info? It works but not sure of purpose.

Route planner...
existing circular (out & back) track > Route planner > results in very short loop track of few 10's of metres of recalculated route from start to end (at nearly same point) because there are no waypoints in example tracks.
Well this is complicated. Such very short route happen right after recalculation, right? It's because definition points are only at start and end.
Try to create such route with latest Locus Map version! ...Anyway with old track or track imported from file, this happen.
I am discussing old track recording, with no waypoints, not creating a new route. Why should the Route planner perform a recalculation when I open this old track? For a circular track this results in no track (nearly same start/ end point). As you say in question below, Route planner does not perform recalculation for change of compute engine, so inconsistent for user/ not the expected behavior.

When using the Route planner if I change the compute engine, why I don't see the route recalculated?
And why it should? System is same as before ... defined engine is applied on new added or changed track parts. There is still option that you wants part compute by one engine and second part by different. Locus gives this option ...
So reverse of previous question/ experience. There is an unwanted recalculation when track opened, but no recalculation when I change compute engine. Could compromise & more flexible solution be to add Recalculate button to the Tools menu so user has full control? Use case: I add start and end point, route is calculated for given profile. I want to see if alternate profile is more suitable. Should the route be recalculated when I switch profile, seems intuitive, otherwise how to force recalculation? Only way at present is to add a unwanted point.

Overall 3.25.3.3 is working much better, although I have confusing BRouter messages at times. I started the Route planner; all working fine; added a few points; then below when I added next point (existing road, BRouter data should exist) I got various error messages (unfortunately often disappear before time to get screen cap). The BRouter message means nothing to an average user, only the developer:
(https://s26.postimg.org/rx98c6lmd/2017-08-29_09_32_26-.png) (https://postimg.org/image/rx98c6lmd/)(https://s26.postimg.org/4ycit9pmd/2017-08-29_09_32_49-.png) (https://postimg.org/image/4ycit9pmd/)(https://s26.postimg.org/wn3rej20l/2017-08-29_09_33_01-.png) (https://postimg.org/image/wn3rej20l/)
Is there a BRouter error code? Maybe Locus can map the error code to a more user-friendly message? In my case the correct RD5 files exist, so I can't yet explain these errors yet. And, the previous route segment (not shown in screen cap) was corrected calculated and displayed.

Issue: start new route > Tools > Add new point > chose point. 2nd Tools > Add new point > chose point. But no route is added. So - "Add new point" is re-positioning the cursor to the point but doesn't add the point. The user still has to tap the + button. OK, valid argument for each side, but "Add new point" is really just "Move to point". I think "Add new point" should actually add-the-point. If incorrect the user can just undo the operation.

Issue: if there is no route, can Tools > Clear plan button be disabled? Then no need for user to see message "Nothing to remove"?

Issue (as mentioned before): Tools > Add new point > there is no "Select on map" option?
(https://s26.postimg.org/m6nnc7305/2017-08-29_10_01_17-.png) (https://postimg.org/image/m6nnc7305/)

Finally: with this intense testing I note phone UI was getting less & less responsive. Implying some task is using more & more CPU. As I was only using Locus it would suggest is related to Locus and/or BRouter. Not a good sign. Can anyone suggest some non-root app or method for display % CPU per process? I don't have any Linux experience in this area of debugging. I tried ES Task Manager but not working like I expect.


Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 29, 2017, 06:53:06
Thanks for a feedback Andrew!
2 days, hmm at least motivation for me to do updates and publish one more Beta version.

Use-case of dashboard ... I need to experiment with it, but my idea is to remove "stats" tab and replace it with dashboard, so everyone may define layout as he wants.

Route planner: ah if I understand correctly ... you open recorded circular track in Route planner and Locus automatically recalculate it? It's a bug, I'll look at this, weird it does not happen to me.

BRouter messages: no error codes from BRouter unfortunately. As you may see, third message is already polished. I do not know previous two, mainly second is interesting as it looks more like problem in BRouter code.

Add new point: I have changed this because it is common situation that you search for a point and result was added to track without option to check if you really wants it. Also with option to add point not just to end of track, it may make sense to let user choose, right?

Tools > Clear : have to ask Petr what is from UX point better. Grey button that cannot be tapped ( and you may not know why ) or button where you get error message when you tap ( but at least know why ).

"Select on map" missing > explained previously "How to? Simply center map center cross to required place and tap on bottom left "+" button. Or even better, long click on wanted place which gives you even three choices where to place new point as you mention below."

CPU usage: cannot help much here as I do not use any such tool, if you find any common pattern why this happen, it will be welcome. In Beta version exists two tools that may help here. If device (Locus) starts to be really slow with simple moving of map, long click on main menu button > Measure method usage and then just move with map for a while. It generates file with recorded all function calls, so it may help me to check if there is all ok. Thanks
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Žajdlík Josef on August 29, 2017, 07:03:23
Hi Menione, the new beta 3.25.3.3 does not go to Xperii M with 4.4 at all. The application crashes at startup.

CZ: Ahoj Menione, nová beta 3.25.3.3 nejde na Xperii M s 4.4 vůbec spustit. Při startu hlásí pád aplikace.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 29, 2017, 09:47:27
Ah thanks, I think I got it ... on my older Xperia it happen as well, perfect, thanks!
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on August 29, 2017, 11:48:39
Use-case of dashboard ... I need to experiment with it, but my idea is to remove "stats" tab and replace it with dashboard, so everyone may define layout as he wants.
clever idea!

Route planner: ah if I understand correctly ... you open recorded circular track in Route planner and Locus automatically recalculate it? It's a bug, I'll look at this, weird it does not happen to me.
correct

Add new point: I have changed this because it is common situation that you search for a point and result was added to track without option to check if you really wants it. Also with option to add point not just to end of track, it may make sense to let user choose, right?
I think the menu name is confusing - it does not add a new point, only move to a new point.

Tools > Clear : have to ask Petr what is from UX point better. Grey button that cannot be tapped ( and you may not know why ) or button where you get error message when you tap ( but at least know why ).
Yes, +/- with each method. There are other places (not Route planner) where buttons are disabled.

So idea of Recalculate button in Tools menu?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: alezy on August 29, 2017, 15:37:08
@menion, can you add possibility to switch between Audio Coach (and disable it) thorough Quick settings or functional panel? My recording profile has training auto-start enabled, and sometimes I want to mute audio coach.
And as you mentioned in help desk theme “Audio coach Quickstart button”
Quote
can't imagine, how this feature should work without active track recording. This "audio coach" simply notify on changes in recorded track
than I have a small problem. When I record my walk to home with AC, and on my route I'm goes to shop, I'm stopping track recording, and after shop I'm resuming it. Track statistics says that my average speed is correct (Recorded_Distance / Recording_Time), but AC calculates average speed as Total_Distance / Total_Time, i.e. it is takes into account time spent in the shop, and underrate my speed  :(
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: lor74cas on August 29, 2017, 16:56:09
@menion, can you add possibility to switch between Audio Coach (and disable it) thorough Quick settings or functional panel? My recording profile has training auto-start enabled, and sometimes I want to mute audio coach.
And as you mentioned in help desk theme “Audio coach Quickstart button”
Quote
can't imagine, how this feature should work without active track recording. This "audio coach" simply notify on changes in recorded track
than I have a small problem. When I record my walk to home with AC, and on my route I'm goes to shop, I'm stopping track recording, and after shop I'm resuming it. Track statistics says that my average speed is correct (Recorded_Distance / Recording_Time), but AC calculates average speed as Total_Distance / Total_Time, i.e. it is takes into account time spent in the shop, and underrate my speed  :(
It's an hard workout if you shop while training.
When I run, I run.
When I go shopping, I go shopping.
When I do the second I suffer more  ;D
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on August 31, 2017, 11:29:54
@alezy: Audio coach in quick settings is not planned. I expect that when someone trains and really care about this training, he is not going to shop meanwhile as @lor74cas wrote :).

Second point is more interesting and known to me. In most cases, audio coach really notify on whole time/speed etc values. Not moving. Not sure how to solve it for now.

New 3.25.3 version on Google Play.
As I mentioned before, I'm leaving in middle of next week for 14 days and because there still were few problems, new version is out. I've also little updated and mainly united text sizes, it's colors etc. based on latest design patterns, so let me know if you find anywhere any serious problems. I'll still be able to publish one more bug-fix version at start of next week ;). And new Beta will be definitely at start of next week.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Žajdlík Josef on August 31, 2017, 11:55:24
New 3.25.3 works on Xperia.

CZ:Nová 3.25.3 už na Xperii funguje.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on September 02, 2017, 09:49:08
why are the numbers of count of POI/Track´s inside data tab in light grey displayed since V 3.25.x ?
black displayed they where  much better visible outdoor
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Bucky Kid on September 02, 2017, 18:38:41
Hello, I see a small change in visible objects behaviour in track planner, so when tapping on icon, a label popups with arrow to open popup menu.
I would suggest to revert old behaviour (label shows + for directly adding the waypoint as via point)
(or control by preferences or config.cfg what is shown on point's label right side during planning). The old behaviour is for track planner more ergonomic, popup menu is OK for normal mode.
I find 3 taps for adding a visible point already too slow.

Edit: eventually, + button can be placed on the left side of the object's label.

_____________________
Sent from my phone using Tapatalk
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on September 03, 2017, 01:09:22
I agree with balloni55 & bucky kid.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 03, 2017, 08:55:55
Hi guys,
I did almost two days, "unification" of styles of whole UI on many places ( because old system complicated me a life and I found many places with less and more different colors & text size compare to rest of app or suggested design tips for latest Android ).

Anyway I'll have to do few more exceptions, like these values or this for example: http://help.locusmap.eu/topic/light-colored-font-in-cache-logs , so thanks for a feedback, I'll try to improve it little bit.

Missing "+" button in "Add new route" function: sorry for this. I have almost finished new route planner and whole app is full of some exceptions because both systems needs to live at once. And this is unfortunate result. I plan one more version before I leave probably tomorrow, so it will be definitely fixed!
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on September 03, 2017, 10:15:55
Hi menion
Quote
@balloni55 : you have to push Arndt little bit :). I have from him some test version for testing of this feature only ...
i´ve wrote Arndt from forum a mail and PM, but since now i didn´t get an answer from him :(
did you have another mail adress to contact him? he hasn´t been active in forum  for a loooong time
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 03, 2017, 16:18:34
Hmm weird. Last communication we had was 12. 8. as I see, so already almost three weeks. Email we use is same as wrote on Google Play (https://play.google.com/store/apps/details?id=btools.routingapp) web , so not some personal secret email. Anyway hope it's only well deserved vacation.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Viajero Perdido on September 03, 2017, 20:51:48
A new glitch in the grey-cache-logs version.  If I go Download Logs, it doesn't refresh to display those new logs.  You have to exit to the map and re-enter the cache info screen to see them.

No biggie because there's a workaround.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 03, 2017, 21:48:45
I read about this problem some time ago, but was never able to simulate it.
Does it happen with caches from database or from caches from Live Map? (or both?) Also with all caches without any difference?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Viajero Perdido on September 03, 2017, 22:42:22
Ah, never mind.

On both my active devices (both Android 6), I uninstalled Locus Free/Beta and rebooted.  Bingo: problem gone.

Like the other issue I mentioned today (Live Map), it must've been due to some G4L confusion over Pro vs Free.

Cheers.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 04, 2017, 06:50:11
Aaaa it may be same issue, you are right. G4L tries to send updated cache logs to second installation of Locus Map. This update data in database correctly, but running installation then do not know about it and does not refresh point screen, this make sense! Thanks, I'll try to investigate when this problem happen!
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on September 04, 2017, 08:29:37
Quote
Hmm weird. Last communication we had was 12. 8. as I see, so already almost three weeks. Email we use is same as wrote on Google Play web
Hi menion
the mail adress here in forum isn´t visible for me, can you please verify if they are identically?
if not i´ll write Arndt once more a mail to adress visble in Google Play
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 04, 2017, 08:41:31
I'm checking it and yes, it's still same email address.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on September 04, 2017, 08:47:04
ok thanks, so i´ll wait....

just for your info:
if device language is set german and locus language is set english
the notification "Locus Map survey 2017/08" is displayed twice, one english one german
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 04, 2017, 11:01:29
Hmm it will be probably side-effect of Free / Pro versions. Both have own indication if notification was already published ...

And BRouter ... I believe Arndt won't be angry if I publish here his version he send me. So version for testing "Nogo" areas in new Route planner attached.

It is not possible to use it in latest public version, so plan: today/tomorrow new final bug-fix version 3.25.4 on Google Play, right after that new Beta with enabled new Route planner etc.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on September 05, 2017, 01:06:21
3.25.4 on Google Play, right after that new Beta with enabled new Route planner etc.
@menion - the new Route planner is getting better and better with each beta release. Well done.

Just reading about Android's largest architectural change, there could be lots of rework for Locus with background processing - https://arstechnica.com/gadgets/2017/09/android-8-0-oreo-thoroughly-reviewed/4/#h1.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 05, 2017, 10:14:39
Thanks Andrew, I also feel like this is going to be really useful (and powerful) tool :).

And new Android 8 ... well, we will see if this will be end of track recording on background on Android or not. For me it looks like it should not be a problem for applications that has active so called "foreground service", which is exactly what Locus Map do. Anyway I'm still waiting till some ROM with A8 appear for any of my devices to test it in the field ...
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on September 05, 2017, 14:12:29
V 3.25.4
FREE and PRO, if i open a geocache listing there are only 2 taps "Basic Info" and "Attachements" :-[
and on FREE no advertising banner at top 8)
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Žajdlík Josef on September 05, 2017, 14:15:41
The new free version 3.25.4, although not a bet, does not show the advertising bar.

cz: Nová free verze 3.25.4 ačkoliv se nejedná o betu tak nezobrazuje reklamní pruh.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on September 05, 2017, 14:43:47
V 3.25.4
FREE and PRO, if i open a geocache listing there are only 2 taps "Basic Info" and "Attachements" :-[
and on FREE no advertising banner at top 8)
solved with V 3.25.5 thanks ;)
do we get a new BETA before you leave in vacation ?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 05, 2017, 15:32:02
@Žajdlík Josef: heh thanks. Locus Free users may consider this as a small bonus from us for next month. I really do not want to create third version today :).

@balloni55: no worry, probably not today, but for sure till I leave ( in Friday ).
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on September 05, 2017, 19:21:32
Quote
why are the numbers of count of POI/Track´s inside data tab in light grey displayed since V 3.25.x ?
black displayed they where  much better visible outdoor
Quote
Anyway I'll have to do few more exceptions, like these values or this for example: http://help.locusmap.eu/topic/light-colored-font-in-cache-logs , so thanks for a feedback, I'll try to improve it little bit.
sorry, i see no considerable improvement :-[

and once again, after i update a geocache from listing i have to reopen it to see the update :-[
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 05, 2017, 22:00:50
No improvements? They are almost black now, compare to previous version :).

With refresh, probably same issue as discussed here: http://forum.locusmap.eu/index.php?topic=549.msg48775#msg48775
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on September 06, 2017, 09:15:43
Quote
They are almost black now, compare to previous version
not at all places
(https://s26.postimg.org/67agmn011/image.png) (https://postimg.org/image/67agmn011/)
Quote
With refresh, probably same issue as discussed here
deinstalling the FREE help :(
i use BETA/FREE over years parallel to PRO with no refrech problems after cache update :-\
so i am curious what happen when i install next BETA ???
So please inform here on new puplished BETA, i am not informed automatically over Playstore now
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 06, 2017, 22:40:20
I have to test little lighter color in the field, but I really believe it will be ok.

Problem with Locus Map & G4L .. uf found (https://github.com/arcao/Geocaching4Locus/issues/91), now it's on Arcao.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: alezy on September 06, 2017, 22:42:48
In last version if I  open "Nearest points" and some categories have long names (e.g. MySuperPoints), than I didn't see direction and distance to points of those categories.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 07, 2017, 14:43:32
*** BETA 3.25.5.1 ***
Try it and let me know. I'm leaving tomorrow afternoon so there is still a time to fix something in case of a serious problem.

@alezy: please screenshot, thanks
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: alezy on September 07, 2017, 15:02:09
@menion, look attachment
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on September 07, 2017, 15:56:35
V 3.25.5.1
Nogo with BRouter-Beta works fine :)
one question, how can i run a recalculation after have deleted a nogo point? see attached screencast
https://www.dropbox.com/s/10n9xmfea7x2w0a/NOGO.mp4?dl=0
and one small concealed text

(https://s26.postimg.org/i2i1iexgl/Draw.png) (https://postimg.org/image/i2i1iexgl/)
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 07, 2017, 17:59:39
@alezy: thanks, I'll look at it

@balloni55: thanks, I noticed this text too, harder to solve without increasing height ...

Anyway with Nogo points, it's a good question. When you add new existing, it's easy. I may test if new point lay on any existing path and recompute this segment automatically. But when you remove any? Recompute everything? Nonsence. I personally solve it with tiny move of one point on side of segment I need to recompute. Any idea?

Also two questions to all.

1) about Nogo areas. Should be ( and think about it for a while ) really useful to define radius of these areas? I'm still not sure how to create a simple UI for this and I'm not really sure if this is needed.

2) just now during planning a trip, I imagined that when I add for example cache into plan as Via point, it only create new point with "Via point" icon and cache name. What a nice idea to copy whole point into track as Via point, what you think? Then should be possible to create complete plan with all necessary data attached directly in track!! Simply turn on/off track to show all that is needed. Simply export track to give other personal whole trip with all that is needed. Useful?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on September 08, 2017, 01:28:21
Anyway with Nogo points, it's a good question. When you add new existing, it's easy. I may test if new point lay on any existing path and recompute this segment automatically. But when you remove any? Recompute everything? Nonsence. I personally solve it with tiny move of one point on side of segment I need to recompute. Any idea?
@menion - it's a similar question I had when I change compute engine profile, and want the whole route to be recalculated. As suggested before, what about Recompute item in Tool menu? Having to workaround with tiny move is silly.

1) about Nogo areas. Should be ( and think about it for a while ) really useful to define radius of these areas? I'm still not sure how to create a simple UI for this and I'm not really sure if this is needed.
I love the circle displayed around the nogo - a nice touch. I use a 50m radius, but with the aid of the new 100m nogo circle the radius is less problematic. I used to have larger ones, but found I never needed them or they caused problems because blocked multiple roads by mistake.

When I add a nogo it would be nice for the undo button to be displayed - consistency. Yes, I can tap the nogo & delete.

When I add a nogo it is not always recognised. Below there are obvious alternates to the nogo but it appears no recalc is performed:
(https://s26.postimg.org/lusyotw3p/2017-09-08_09_14_11-.png) (https://postimg.org/image/lusyotw3p/)
Once the nogo was not recognised/ not being bypassed, no other nogos worked either. Recalc is not performed.

I also found (only sometimes) when I tap the nogo, I get this dialog instead. Tapping the track was not useful:
(https://s26.postimg.org/ahb0rdayt/2017-09-08_09_25_22-.png) (https://postimg.org/image/ahb0rdayt/)
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Žajdlík Josef on September 08, 2017, 06:59:39
Hello Menion, I would recommend that NOGO points be moved to a separate function, krera would be part of the route planner. NOGO would then remain permanent or temporary. For example, when repairing the road from March to September, I would create points in the NOGO closure point valid until the end of September. On the contrary, at the broken road site, I would have created a permanent nogo so Brouter would never drive me when driving on a road bike.

CZ: Ahoj Menione, doporučil bych NOGO body přesunout do samostatné funkce, krerá by byla součástí plánovače tras. NOGO by pak zůstávaly trvalé nebo s dočasnou působností. Například při opravě silnice od března do září bych si vytvořil v místě uzavírky NOGO body s platností do konce září. Naopak v místě rozbité silnice bych si vytvořil trvalý nogo, aby mě tudy Brouter nikdy nevedl když jezdím jen na silničním kole.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: matmas on September 08, 2017, 14:24:03
Hello guys

I liked a lot the new route planner. Amazing the info bar with graph at the bottom of the screen.

I found a bug and I have a suggestion.

Sometimes when you click on a track (even before using route planner) on the caption appears a + sign and the app crashes.
(https://uploads.tapatalk-cdn.com/20170908/8007bed1bc60f53353e1d39d1fc1c884.jpg)

Normally you have a >
(https://uploads.tapatalk-cdn.com/20170908/46b3d7eccbfd3db5bc4265bad770be75.jpg)

The suggestion is not have the track recalculated when you use route planner on an existing one, or at least ask. You may even not notice the recalculation on longer tracks and you may loose good portion while attempting to correct the bad ones. This may happen frequently   when you use more the one engine for routing and you unlikely remember what was used in that specific track.

Inviato dal mio SM-G900F utilizzando Tapatalk

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Bucky Kid on September 10, 2017, 17:04:36
I confirm the bug reported by matmas.
Right side action for visible object label is not changed to popup menu after closing route planner (crash on tap).

Edit:
+ Yet some bug in tracks manager alphabetic sorting (tracks starting with J, K precede other tracks.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: zossebart on September 18, 2017, 13:55:42
First of all, I'm very impressed by the new route planner!

- Session save/restore: excellent, I didn't dare to ask for this feature and now you've implemented it!  ;D
- Undo/Redo: perfect!
- Info bar/graph: I was about to post this as an idea in helpdesk, seems you read my mind and implemented it right away!  ;D ;D ;D
- NOGOs: very nice, can't wait to test it! (haven't had time to install new brouter testing version yet)
- add viapoint between two existing points of the route: very helpful!
- possibility to invoke trackplanner with existing track: a dream come true! Never ever re-plan a track because you forgot something (e.g. a via-point) (and it's even working with gpx-exported/re-imported tracks!  :) :) :) )

About NOGO radius: It would be very nice to be able to change the radius, because sometimes you just want to block one small section of a path (and not the neighbouring path also), the other time you maybe want to block a whole village!
I imagine it could be nice to have radius editing controls similar to brouter-web (create a nogo and afterwards edit it in brouter-web, this gives a handle for the center and one for the radius). But maybe it's too difficult to implement it. Also, I'm not sure if this method is suitable for small phone screens with your finger(s) occupying the screen!? (on the other hand, quick measure seems to work reasonably well)

About your idea of saving all data of a viapoint (e.g. a Cache) into the track: yes, please! Also export this info into gpx to share with friends: would be great!

ps: I can also reproduce the bug matmas discovered!

regards,
Zossebart

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 21, 2017, 14:39:46
Hi guys,
hope you had a good time during my vacation. Well we were in Tuscany, weather was average ( which is fine because I was not forced by Hanka to be on beach all the time ), Locus was working surprisingly well and from 8 offline navigation apps I prepared for test and inspiration, we ended with Locus & BRouter. Except testing at start with other apps, almost 3k km ride was made with this combination ... and again quite good experience, mainly with quick NoGo points from navigation menu :). And all nav apps quick sucks to be true ... maybe I'm too used to use Locus :)

And now back to work.
@Andrew Heard:
@menion - it's a similar question I had when I change compute engine profile, and want the whole route to be recalculated. As suggested before, what about Recompute item in Tool menu? Having to workaround with tiny move is silly.
I have to think about it later. What you wants means that one tap recompute whole track with define routing settings right? This is something that probably most of apps do automatically, but since begin, Locus works differently and always allows to set each segment of route separately.

Otherwise I was working whole yesterday on some bugs reported on help desk and finally today I'm doing some smaller improvements in route planner, so please wait on next Beta ( probably tomorrow ), because we discuss some final ( hope ) improvements in route planner. Thanks
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: zossebart on September 21, 2017, 15:28:12
Hey, welcome back!

hope you also got some time to rest and relax!?

What do you mean by "quick NoGo points from navigation menu"? Is this already in BETA?

Btw.: I forgot to praise yet another idea you implemented in BETA: Dashboards in Track Statistics! Great Idea (I assume you will provide a default Dashboard for not so experienced users?)!
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 21, 2017, 16:02:52
Sure, no worry ;).
Ah, this is probably not yet even in Beta, hmm :). My feature where in navigation menu ( click on next-command arrow during navigation ) is button that adds NOGO point under map center and force recalculate, so when you see, there is no way during navigation, with few clicks you may recompute detour.

Yes dashboard ... I tought it will be my evening relax, but my try to allow creating 1:1 same dashboard as is current statistics tab, ends on neverending list of necessary settings for every item ... padding left/top/right/bottom, same for margins, same for border lines and here even width and color of border lines ( separators ) ... I have to firstly find some better style of UI otherwise list of edit options will have no end ... probably some tabs, I'll see anyway it is something I really wants to do and this system should in the end replace track "statistics" tab completely and also statistics in left track recording panel ... later ;)
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on September 22, 2017, 00:54:04
@Andrew Heard:
@menion - it's a similar question I had when I change compute engine profile, and want the whole route to be recalculated. As suggested before, what about Recompute item in Tool menu? Having to workaround with tiny move is silly.
I have to think about it later. What you wants means that one tap recompute whole track with define routing settings right? This is something that probably most of apps do automatically, but since begin, Locus works differently and always allows to set each segment of route separately.
Yes I appreciate the complication with independent segments. As you say other apps already do this, and I therefore guess, is the most common use-case. This is, only a very small % of user's tracks will have more than one segment+profile combination. So if a user selects this "Recompute" menu item, Locus could recompute each segment+profile combination?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on September 22, 2017, 01:04:49
Yes dashboard ... I tought it will be my evening relax
strange way of relaxing ;)

try to allow creating 1:1 same dashboard as is current statistics tab, ends on neverending list
does default/user dashboard have to be as perfect as current precisely designed/ well presented stats tab? If I had to choose between A) flexible user defined stats using current dashboard editor or B) existing fixed stats tab, I would vote for A.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: john_percy on September 22, 2017, 10:22:17


This is, only a very small % of user's tracks will have more than one segment+profile combination.
I have frequently had to change profiles during route planning where the map is imperfect. Sometimes I have had to manually draw part of a track where paths are missing or don't join up. Sometimes I have changed the profile to choose different options.


Sent from my XT1039 using Tapatalk

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: zossebart on September 22, 2017, 13:59:05
Sure, no worry ;).
Ah, this is probably not yet even in Beta, hmm :). My feature where in navigation menu ( click on next-command arrow during navigation ) is button that adds NOGO point under map center and force recalculate, so when you see, there is no way during navigation, with few clicks you may recompute detour.

Sounds great! Would you please be so nice and add it to next Beta? I've had several situations in the woods where a path was heavily overgrown where this feature would have been extremely useful!

Yes dashboard ... I tought it will be my evening relax
strange way of relaxing ;)
I agree with menion ;-)
I also thought of a nice relaxing "sofa task" immediately :D

This is, only a very small % of user's tracks will have more than one segment+profile combination.
I have frequently had to change profiles during route planning where the map is imperfect. Sometimes I have had to manually draw part of a track where paths are missing or don't join up. Sometimes I have changed the profile to choose different options.

I also use track planner this way and I'm very happy that Locus offers the possibility to do so. Maybe menion could save the used profile for each segment with the track in order to use it for (partial) recomputation later? But maybe this could get complicated if you delete or update profiles and want to recompute an old track you created earlier with the old profiles?

try to allow creating 1:1 same dashboard as is current statistics tab, ends on neverending list
does default/user dashboard have to be as perfect as current precisely designed/ well presented stats tab? If I had to choose between A) flexible user defined stats using current dashboard editor or B) existing fixed stats tab, I would vote for A.

+1, I would also vote for option A!
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on September 22, 2017, 14:05:15
@zossebart
Quote
Would you please be so nice and add it to next Beta?
it´s also available in current Beta
to get it work install first
BRouter 1.4.8.b.apk from post #94
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: lor74cas on September 22, 2017, 14:19:27
Sure, no worry ;).
Ah, this is probably not yet even in Beta, hmm :). My feature where in navigation menu ( click on next-command arrow during navigation ) is button that adds NOGO point under map center and force recalculate, so when you see, there is no way during navigation, with few clicks you may recompute detour.

Sounds great! Would you please be so nice and add it to next Beta? I've had several situations in the woods where a path was heavily overgrown where this feature would have been extremely useful!

Yes dashboard ... I tought it will be my evening relax
strange way of relaxing ;)
I agree with menion ;-)
I also thought of a nice relaxing "sofa task" immediately :D

This is, only a very small % of user's tracks will have more than one segment+profile combination.
I have frequently had to change profiles during route planning where the map is imperfect. Sometimes I have had to manually draw part of a track where paths are missing or don't join up. Sometimes I have changed the profile to choose different options.

I also use track planner this way and I'm very happy that Locus offers the possibility to do so. Maybe menion could save the used profile for each segment with the track in order to use it for (partial) recomputation later? But maybe this could get complicated if you delete or update profiles and want to recompute an old track you created earlier with the old profiles?

try to allow creating 1:1 same dashboard as is current statistics tab, ends on neverending list
does default/user dashboard have to be as perfect as current precisely designed/ well presented stats tab? If I had to choose between A) flexible user defined stats using current dashboard editor or B) existing fixed stats tab, I would vote for A.

+1, I would also vote for option A!
Umm in this forum there are advanced users and it's easy to imagine that we all vote A. But what does a normal user want? Something easy, ready to use out of the box. So Ok with customizable menu but at a fresh new install the new locus user must find the a user friendly stats menu with the most common data.

Inviato dal mio SM-G800F utilizzando Tapatalk

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 22, 2017, 14:32:33
*** BETA 3.25.5.2 ***
- except many bugs you reported over last 14 days, there is also little bit polished Route planner of course.

Summary of situation:
Route planner
- really wants to publish it in next bigger version ( +- 2/3 weeks )
- NOGO areas won't be yet published
- "recompute whole route" suggested by Andrew will be considered as easy alternative how to compute whole route at once with single defined parameter

Dashboard in track statistics
- understand you wants at least something, but in this case, till dashboard won't be perfect, I'll not switch it. For now, feel free to use it in Beta versions as secondary tab
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: matmas on September 22, 2017, 16:00:44


*** BETA 3.25.5.2 ***
- except many bugs you reported over last 14 days, there is also little bit polished Route planner of course.

Summary of situation:
Route planner
- really wants to publish it in next bigger version ( +- 2/3 weeks )
- NOGO areas won't be yet published
the bug I found was resolved
new route planner in 2/3 weeks
no go areas not yet published: I tried few minutes with the new version and they  are a kind of magic working flawlessy but I understand if you want test then more

Quote
- "recompute whole route" suggested by Andrew will be considered as easy alternative how to compute whole route at once with single defined parameter


I'm asking really to reconsider this because  I tried to edit with route planner several tracks and all of them have been fully recalculated .  On long route this could be a mess. I often use two or more profiles during the same route.

I think recalculation  should be procided as an option and generally speaking the recalculation should happen "between two green dots" when you move a green or red dot in between   




Inviato dal mio SM-G930F utilizzando Tapatalk

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Christian on September 22, 2017, 20:03:15


This is, only a very small % of user's tracks will have more than one segment+profile combination.
I have frequently had to change profiles during route planning where the map is imperfect. Sometimes I have had to manually draw part of a track where paths are missing or don't join up. Sometimes I have changed the profile to choose different options.


Sent from my XT1039 using Tapatalk
+1
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on September 23, 2017, 01:59:43
This is, only a very small % of user's tracks will have more than one segment+profile combination.
I have frequently had to change profiles during route planning where the map is imperfect. Sometimes I
@John_Percy I also sometimes change profiles during route planning where the map is imperfect. But my gut feeling is that the average user would not be aware of this feature. Operation should be most intuitive for the common use-case but flexibility available that Locus is legendary for. If the user chooses to perform a full/ manual recalculation, each segment would be recomputed with its associated profile. This implies (if it is not already done) each route segment profile metadata needs to be saved/ restored.
 
If I delete a NOGO point how do I force the route (segment) to be recomputed? The only workaround I can see is to modify a point. Deleting a NOGO should force a recompute just like deleting or modifying any other point.

@menion
1. the route planner gets better & better. I note the via/ navigation/ definition point icons are now a little larger, easier to tell apart. For me they are the optimum size. This sort-of new concept definition point is good but I think the actual name "definition" is long and cumbersome. I can't think of a better one, maybe others can. The purpose of Via and Navigation points are fairly intuitive but a better name may help describe a Definition point?

2. In this 1st video I think the Route Planner is undoing 2 steps instead of just the last one. I add a 1st point, then a second/ final point, all good. Now I move the 1st point to another location. Still good. Now though I tap undo, and would expect the 1st point just to move back, but observe that the 2nd is also deleted.
https://youtu.be/tEmP8YMVygw (https://youtu.be/tEmP8YMVygw)

3. In this 2nd video, which is just the same route in the Route Planner, it seems Locus has forgotten the BRouter profile. The profile, unchanged from the 1st video, is set to Libor's Tertiaries, but when I add the next definition point a straight line is drawn by mistake instead of following the road.
https://youtu.be/eLLmdtoEbFc (https://youtu.be/eLLmdtoEbFc)

4. Previously when I use the Route Planner for an existing out-and-back or loop recorded track the route was recomputed and I ended up with all of the loop truncated - zero length track. I notice this has now been fixed, the route is preserved; thanks. However I observe an orange msgbox "Distance between points is too short". Is this helpful?

5. Tap on a "track point" - popup menu allows change to a blue Navigation point or a green Definition point. Why no option to change to a Via point? Tap on a Definition point and it can only be changed to a blue Via point. Maybe there is a good programming reason, but for consistency why not allow any point to be converted to any other point?

6. Could either the Navigation or Via point be a color other than blue? And why are there a few smaller red track point icons in the route? I guess these are Track points but do they serve any purpose because I can tap anywhere in the track to (sometimes) edit the closest track point. The red is very hard to see against a magenta route so maybe there is a better choice of color here too?

7. In this 3rd video, I modified a simple out-and-back recorded track to force partial loop. When I tap on the track I get this popup menu of irrelevant options; and no option to choose a track point, or convert to another type of point. When the track is green (in background of popup menu), the little black direction arrows are visible inside the track, but with the magenta route color the direction arrows are impossible to see.
https://youtu.be/uKPaoQIQPG4 (https://youtu.be/uKPaoQIQPG4)
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: 0709 on September 23, 2017, 09:15:26
Quote
a better name may help describe a Definition point?
Shaping Point ?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on September 23, 2017, 11:54:47
Good idea. I think English speaking users would understand the meaning of a "Shaping" point more readily than a "Definition" point. Also less characters. Then the art of translation.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: T-mo on September 24, 2017, 17:40:10
the new route planner is awesome :)
one issue I had to fight with: popped-up marker-popups :D
Of course they appear when you
- touch and select a regular connection-/via-point
- long-press the map
I did my very best but I was still not able to close those popups to see the map without any overlays, so
- long-pessing map > new detailed window with basic infos, then back
- adding a new point and deleting it
..still workarounds
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 24, 2017, 22:06:02
@Andrew Heard:
You always write so looong posts, best to number paragraphs hmm? ;) ( edited ).
1. "Shaping point" sounds good, thanks @0709

2. issue fixed, thanks for video, it helped

3. unable to simulate, does it happen to you always? Is this profile working for you at all?

4. it was still not fixed, what happen to you is just unwanted problem. Anyway consider this as solved for now ( next version ). @matmas complained on this before ( and maybe someone else ) and I was still not sure what is a problem and fortunately it happen to me as well, so finally fixed in next version.

5. does it make sense to change trackpoint to via point? I expect that is track usually automatically computed along some road and if there is something interesting along, it is not directly on track. So why not long click on interesting place ( if there is not yet point ) and add this point into middle of track as via point?

6. I hope, I'll get an idea for a regular icons instead of these blue and green once. About red ... they belong to older system, but I believe, they are still very very useful. Simply grab them with finder and move them. It will automatically create shaping point that you may immediately place where you wants.

7. hmm you cannot get here popup for trackpoint because you tapped on place where are three tracks, so you firstly needs to choose the right one. If you choose track from list, it should offer trackpoint-popup, does it happen?

@T-mo: on main map screen, when popup is visible, back press button hide this popup. I was a while thinking about same here .. should it help? Hmm ...
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: matmas on September 24, 2017, 23:24:51

4. it was still not fixed, what happen to you is just unwanted problem. Anyway consider this as solved for now ( next version ). @matmas complained on this before ( and maybe someone else ) and I was still not sure what is a problem and fortunately it happen to me as well, so finally fixed in next version.


I wasn't able to understand the difference between the via point and the shaping point.

After some tests it seems that when you use route planner on an existing track it remembers via points and forgets shaping points.

So if you shape a "U" track with only shaping points and you edit again with planner it straightens the track . If you use via point this does not happen.

(https://uploads.tapatalk-cdn.com/20170924/7d54729b188a115e5ba560d6028dd8e9.jpg)

Imagine  you have the red route:
- if it was made with shaping points only when edited it is recalculated to the blue
- if it was made with  via points (i.e.
the blue arrow on the top) the recalculation get same result as before only if the routing profile hasn't been changed. I mean  that the original track is never kept unchanged, sometimes it is recalculated with the same output as before.

Here you see the green one with only a portion that is as before because the first part (on the right) was drawn with shaping points.

I think this is quite confusing. Why do we need shaping point and via point with a different behaviour  ?




Inviato dal mio SM-G930F utilizzando Tapatalk
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on September 25, 2017, 02:01:27
@Andrew Heard:
You always write so looong posts, best to number paragraphs hmm? ;) ( edited ).
My QA background. I can make them shorter - report less issues, report with less detail. But I hope the feedback is useful. Sorry for another looong post :(

3. unable to simulate, does it happen to you always? Is this profile working for you at all?
Profile is 100% reliable with external BRouter method, 99% reliable with beta Route Planner. Problems only after intensive QA testing of Route Planner. No problems today. Is it possible communication with BRouter may silently fail & Locus reverts to straight line track segment? I can't reproduce. A few weeks ago I wrote Locus getting slower & slower - does Locus create a new thread for each BRouter operation? If a thread never completes, will subsequent threads also fail/ block, and could this explain CPU load getting higher & higher?

5. does it make sense to change trackpoint to via point?
It prevents the router from moving the track to some other road if the whole track is recomputed. It appears there are all special (unnecessary) rules for which point can be converted to another type of point.

6. About red ... they belong to older system, but I believe, they are still very very useful
thanks, finally understood

7. hmm you cannot get here popup for trackpoint because you tapped on place where are three tracks,
now understood - to me these 3 "tracks" are just 3 overlapping track "segments" of the same current Router Planner track. The to/ from names <A> & <B> are meaningless to the user, and maybe the term "Track" could be "Part" or "Segment"? Examples:
(https://s26.postimg.org/vc8pmtoxh/image.png) (https://postimg.org/image/vc8pmtoxh/)
(https://s26.postimg.org/ub8gxp7xx/image.png) (https://postimg.org/image/ub8gxp7xx/)
(https://s26.postimg.org/5w08wn911/image.png) (https://postimg.org/image/5w08wn911/)

7. ...If you choose track from list, it should offer trackpoint-popup, does it happen?
yes

8. delete a NOGO - should this be undoable?

>Why do we need shaping point and via point
@   matmas - for me a shaping point can be considered an unnamed via point. The UI for shaping points is faster.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 25, 2017, 09:37:04
@Andrew Heard
nono posts are fine and really useful. I just don't like complicated responding when I wants to include also "quote" on certain part of text ... like you did in your last post. How are you doing it? Manually by copy & paste of texts like "[/quote author=menion link=topic=5827.msg48978#msg48978 date=1506283562]" and edit etc? It is really long process for longer texts ...

3. it is possible that communication failed, but in this case there should be some orange toast with error message. Anyway if communication is interrupted, system should terminate it automatically after a while. Slowing of Locus was maybe side effect of one serious problem I found and solved a week ago, so let me know if it will be better in new Beta version(s).

5. make sense, I'll re-think it, thanks

7. good point, thanks

8. nogo currently works as quite independent system, I believe it does not belong directly into this undo/redo system. They keep added even if you just close unfinished planning etc, so they really should stay independent.

@matmas
main usage of via-points compare to shaping points:
- they are visible on track after save
- navigation > navigation system should read that you are passing these points
- navigation > navigation system when recalculate track for some reason, search for nearest via point. If no is found, target of recalculation is final point instead

About storing & restoring track in route planner ... try it please also with a new track created in latest Beta versions. They should already have stored full track configuration even with shaping points. It just needs to be created in latest Beta versions.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Taras D on September 25, 2017, 15:38:54
The current system uses three kinds of points to define a "Route"

1) Shaping/Destination Points
2) Via Points
3) Navigation Points

Why isn't the most basic of these three points simply called a "Route Point"? Or "Routing Point"?

Would it not be clear that you define a Route using Route/Routing Points? (Instead of Shaping or Destination.)
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: 0709 on September 25, 2017, 17:25:09
Locus does not create a route...but track(trk).Thats why I do not suggest as in a gpx route (rte) we have routepoints) (rtpte.) Just for now I use Shaping Point.

Attached gpx: Has also Info Points": Same (re)calculate functionality as standard "Via Point".
Locus partly understand the gpx nav style. But the <desc> info is not displayed.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Taras D on September 25, 2017, 18:50:14
Quote
Problem = Locus does not create a route...but a track to be navigated along.
...
Locus do not generate you a  (technical) route (gpx = rte) but generates you a track (trk) so has trackpoints (trkpt). 

I understand the underlying technical aspect but is it relevant? After all, the function is called Route Planner.

Regardless of the function's output format, its purpose is to plan a route (i.e. the path of your planned trip). You create Route Points to indicate where you want the route to go.

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on September 26, 2017, 01:30:53
@Andrew Heard
nono posts are fine and really useful. I just don't like complicated responding when I wants to include also "quote" on certain part of text ... like you did in your last post. How are you doing it? Manually by copy & paste of texts like "[/quote author=menion link=topic=5827.msg48978#msg48978 date=1506283562]" and edit etc? It is really long process for longer texts ...
@menion - yes - I manually (tediously) copy & multiple paste/ edit the quote; is probably only an issue when replying to multiple points/ issues at once. Happy if you can suggest a better alternative?

3. it is possible that communication failed, but in this case there should be some orange toast with error message. Anyway if communication is interrupted, system should terminate it automatically after a while. Slowing of Locus was maybe side effect of one serious problem I found and solved a week ago, so let me know if it will be better in new Beta version(s).
There was no orange toast error, and certainly yesterday with hour of intensive route planner testing for my reply I didn't have a single problem (slow CPU or straight line or other BRouter failure) so I think "one serious problem" was fixed! Well done.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on September 26, 2017, 01:50:57
The current system uses three kinds of points to define a "Route"

1) Shaping/Destination Points
2) Via Points
3) Navigation Points

Why isn't the most basic of these three points simply called a "Route Point"? Or "Routing Point"?

Would it not be clear that you define a Route using Route/Routing Points? (Instead of Shaping or Destination.)
@Taras - that's the discussion we are now having. Destination Points are a beta-only feature. No documentation/ manual yet so perfect time to get best outcome. For me, all 3 types of points are routing points - they are all used to influence the path of the route. If I do a search for "garmin Shaping Point definition" I find there is already widely recognized terminology so why invent yet another term. It appears this Garmin topic (https://forums.garmin.com/forum/mac-windows-software/windows-software/basecamp-aa/22738-pois-waypoints-via-points-shaping-points-101) is quite relevant to the Locus situation.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 26, 2017, 10:52:06
Hmm, isn't what I wrote to matmas here http://forum.locusmap.eu/index.php?topic=5827.msg48985#msg48985 good enough reason? Maybe I'm only one who find this concept useful? And if so, you expect to all points behave like "via points" or like "shaping points"?

@Andrew Heard: I also do not know better method how to answer with quote, that's why I complain on this system little bit :).


Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on September 26, 2017, 11:00:06
Hmm, isn't what I wrote to matmas here http://forum.locusmap.eu/index.php?topic=5827.msg48985#msg48985 good enough reason? Maybe I'm only one who find this concept useful?
A useful concept for me too.

It seems that Shaping points behave like unnamed Via points? Although Via points inside a track can be exported & correctly restored on import. Could a Shaping point be treated like an unnamed Via point for export/ import?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 26, 2017, 11:06:44
Is it really necessary? I always considered these green shaping/definition/whatever points to be only a helpers when creating routes, nothing more. They just say "hey, I wants to ride here and here, but I definitely do not want to be notified about these places". So they are "lost" once track is created and saved ( in latest versions they are stored internally and restored in route planner, but again just for use-case of route planning ).
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: matmas on September 26, 2017, 13:44:08
@menion Now I understand what's the difference between the two.

If you need two of them or not, if you need to export as gpx as @Andrew suggested or  not, I don't know. We will probably discuss for months and therefore it's a choice you should made. IMO if you have two different object is better to have them really different (as it is) then more or less same (as unnamed via points).

I did a test with the available beta and a fresh track and seems the shaping points are not recovered in the track when you edit with route planner.
(https://uploads.tapatalk-cdn.com/20170926/39925e2309cd57e278241b79b2618b24.jpg)

New track. on the right you see a via point in blue e several shaping points here and there.

(https://uploads.tapatalk-cdn.com/20170926/c27d4cc6f0edeff60abc071da56c3523.jpg)

If you save and edit the route has been recomputed and  only the via point has been used.

If you transform the via point in shaping point you have this after editing again:

(https://uploads.tapatalk-cdn.com/20170926/c8927676f00d6bcbc2ce3311b9bc44ed.jpg)

From you words I understand this is not the intended behaviour.

If I have two put my two cents is that the track is not recomputed when you edit it with route planner

 It should behave as it does the moment before saving, I think is the more natural behaviour.

If you want a recalculation, make a fake move on a shaping point or ask to compute it all with a proper menu entry.

(BTW great thing that if you exit without saving you can restart where you left )

As always thousands thumbs up   for your work!

Inviato dal mio SM-G930F utilizzando Tapatalk
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: zossebart on September 26, 2017, 15:32:29
@Menion:

Thanks for adding nogo button in navigation menu, tested it at the weekend, works as expected! (despite the fact that I first forgot to move the cursor to another position than my current location before adding the nogo  ;D ).

Hm, the more I think of it, the more I want to say: please also save shaping/definition points into exported gpx. Because for me, they belong to the track the same way via-points do, they are essential for the shape of the track (and the user normally sets them intentionally).
This way, editing the (re-imported) track later is easier and you immediately see the intention of the creator of the track.
In the resulting track (when not in routeplanner mode) they should stay invisible and of course they should be ignored when recalculating in navigation mode (as it is now).

Any progress about nogo radius user interface?
Did you come to a conclusion about export of full via point data by now?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Taras D on September 26, 2017, 16:35:13
@Andrew

Thanks for the link! The 77th post in that thread (https://forums.garmin.com/forum/mac-windows-software/windows-software/basecamp-aa/22738-pois-waypoints-via-points-shaping-points-101?p=947207#post947207) (whew!) sums up my own experience with using Basecamp (i.e. its use of undocumented terminology).

To put it politely, the term "Shaping point" is used very sparingly in Basecamp. Searching for "shaping points" in Garmin's online Basecamp documentation produces no results (it finds many matches for "points"). The documentation uses the generic term "Route Points" (http://static.garmincdn.com/basecamp/4_6/en/GUID-38F25A2C-95BE-4613-97B0-383488884B37.html). HOWEVER, if you right-click a "route point", ta-dah!, there in the pop-up menu you see "Remove shaping points"! It also appears in (some) Nuvi documentation.

I defer to my wiser colleagues, who are clearly better versed in Basecamp's "secret language" than I, and accept the term "shaping point". :)

The 77th post also provides an explanation for the difference between "Shaping Points" and "Via Points".

Via points vs shaping points

Is this how the Route Planner is handling Vias and Shaping Points?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Žajdlík Josef on September 26, 2017, 19:24:47
Views with a new beta version.
1) Keyboard export panel is great, good work. Little, but pleased.
2) The NOGO points work great, but for the practical use they are too big - picture. If I want to block only one street because it is inconvenient, the range of the NOGO point closes the surrounding streets. I recommend adding a size slider when creating a new NOGO point - picture.

CZ:
Postřehy s novou beta verzí.
1) panel pro export bez klávesnice je skvělý, dobrá práce. Drobnost, ale potěší.
2) NOGO body fungují skvěle, ale pro praktické použití jsou moc velké - viz. obrázek. Pokud chci zablokovat jen jednu ulici protože je neprůjezdná, rozsah NOGO bodu mi uzavře i ulice okolní. Doporučuji při vytváření nového NOGO bodu přidat posuvník nastavující velikost - viz. obrázek.

(https://s26.postimg.org/imfxq2xrp/Screenshot_2017-09-26-15-11-04.jpg) (https://postimg.org/image/imfxq2xrp/)
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on September 26, 2017, 19:29:07
Quote
I recommend adding a size slider when creating a new NOGO point - picture.
+ 1 :)
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on September 27, 2017, 01:34:24
@Taras - I'm certainly not fixed on the term "Shaping" point. It is more meaningful & appeared on the face of it to be a more widely used term than "Definition" point. You & @0709 (& like the idea) observe a Shaping point is simply a silent, unnamed, unannounced Via point. So maybe this 3rd type of point doesn't even need a separate name? It's just an unnamed Via point? That could solve the next point...

@Menion - I'm strongly in support of @zossebart (also @matmas I think) that unnamed Via/ Shaping points are preserved in the metadata when the route plan is saved to a track. @0709 has indicated these silent Via points are then preserved on an export/ import GPX round-trip.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: poutnikl on September 27, 2017, 07:42:00
@Taras - I'm certainly not fixed on the term "Shaping" point. It is more meaningful & appeared on the face of it to be a more widely used term than "Definition" point. You & @0709 (& like the idea) observe a Shaping point is simply a silent, unnamed, unannounced Via point. So maybe this 3rd type of point doesn't even need a separate name? It's just an unnamed Via point? That could solve the next point...

In some sense, shaping points aka unnamed viapoints are just viapoints, to just go through.
In some sense, viapoints aka named viapoints are not really viapoints, but route POIs to visit..
Both are worthy to be kept when route is saved or exported.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 27, 2017, 10:29:57
Thank you guys for useful discussion. Seems that description on Garmin web page ( mentioned by Taras ) exactly describe system I have in mind here. So for now final decision is "Shaping points", is it's best describe reason of these points and also match "existing" used terminology.

Shaping points are not stored in metadata of saved track as I mentioned earlier. In latest Beta is remaining problem that when you start Route planner from submenu of any track, and any routing option ( other then "manual draw" ) is selected, autorecalculation starts automatically which cause lost of these shaping points. Will be fixed in next version.

Export of shaping points into GPX is currently not implemented. Still not sure, if this is needed at all ... we will see ;)
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Taras D on September 27, 2017, 18:31:31
I found useful information about routing with Garmin devices here: http://www.poi-factory.com/node/6656

Garmin has a broad range of devices and they don't all behave the same way. According to someone on poi-factory, devices made before 2013 (like the Nuvi series) don't support shaping points correctly (they treat them exactly like via points ... and announce them).

This post (http://www.poi-factory.com/node/45037) includes a summary of the characteristics of shaping points:

--------------------------------------------------------------------------------------------------------
Shaping Points Advantages:
1- You will not be alerted as you're navigating and arriving at a shaping point as you are when using waypoints/vias.
2- If you deviate purposely off your route, the unit will skip the upcoming shaping point and navigate you to your next shaping or waypoint.
The disadvantage of using only waypoints is when you deviate purposely off your route the unit will try to route you back to the waypoint that you didn't go through.
3- When using shaping points with certain units you're able to manually skip an upcoming shaping point.

Note: Shaping points do not contain arrival time or distance between points information.

--------------------------------------------------------------------------------------------------------

I can't find the post now but I recall reading Shaping Points are exported as <rtept>. I guess this is easy to confirm by exporting a route (containing shaping points) from Basecamp and examining the output.

This is fascinating stuff and I look forward to using Route Planner when it arrives in the next (full) release.


PS
I like Josef's "floating slider" suggestion for adjusting the size of NoGo points.

Should the floating slider prove to be difficult to implement (avoid overlapping other onscreen controls) or to use (it's a narrow target and a finger tap might be misinterpreted as touching the map), then an alternate is to use FABs (Floating Action Buttons).

When a NoGo point has focus, two NoGo-sizing buttons could appear above the existing two zoom buttons ("+" and "-") on the right. The icon on the upper button can be a large circle (to indicate increasing the size of the NoGO) and a smaller circle on the lower button (to indicate reduction of the NoGo's size).

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on September 28, 2017, 00:18:07
Shaping points are not stored in metadata of saved track as I mentioned earlier.<snip> Will be fixed in next version.
@menion - can you clarify your quote - Shaping points are not saved in Locus internal database track metadata or external GPX file metadata? In my testing 3.25.5.2 Shaping points are saved to the internal database track metadata.

<snip> Will be fixed in next version.
What will be fixed?  My interpretation is most users in this forum topic would like Shaping points preserved.

Export of shaping points into GPX is currently not implemented. Still not sure, if this is needed at all ... we will see ;)
Export of shaping points into GPX (Locus V1.1) would allow full round-tripping of saved Locus-created route.

With the Route Planner it is faster to add a Shaping point than a Via point (naturally). Most times I don't need any Via points. BRouter automatically creates all Navigation points. If I find I want to steer the route along some different road then I would simply add Shaping points as necessary. But I do want to be able to edit that track later (not just restoring the route plan) and have any existing Shaping points restored for further editing.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: zhaelon on September 28, 2017, 04:35:47
Hey everyone,

Please excuse me if I did miss already discussed points. I tried to read the threads but may have skipped over some parts.

I would like to comment on the new route planner, as I make heavy use on the old one (about 30k miles planned with it) and just tested it during the last 2 days for our motorcycle vacation (still almost 1 week left).

First off, I really like the new design and it adds a lot of flexibility.

Please add me to those hoping that the meta data about the current routing profile is stored on a per point basis and that a recompute function is added using this information. I also have to switch profiles a lot and just by dragging a point (for example on a small byroad) the current profile is applied, which is usually the wrong one messing up a previously good route ;-)

What I am currently unable to do (maybe I missed it, as I only tried it a few times):


That said, the route planner makes planning our motorcycle trips easier (allowing to better insert points in between) but makes it a lot more difficult by preventing access to several (for us) critical options (poi/track, map, themes). Also I do hope that the distance value will be changed / enhanced to display the distance from start and distance to end instead of distance to GPS.

Another thing which I would love to see (though I could not say if it is included or not): I know that the Locus Maps have a POI database. As I never downloaded anything from the Locus Store, I do not have them and use the free vector maps without them.
Nevertheless, it would be great for motorcycle trip planning if there was an option to show POI of a certain group (for example gas stations) *along the route* (say +- n km/mi, optional value). That should not be a dynamic option but a 'display GROUP (select) along the current route' button, which helps identify a POI (or multiple) to add as via point (or mark as 'visible') and then hide everything else again.

Currently I use Navigon Cruiser or Here we go (both work on Here maps and its POI database) to find the nearest gas station offline and add them manually to the route :-)

Best wishes,
zhaelon
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on September 28, 2017, 08:47:02
Nevertheless, it would be great for motorcycle trip planning if there was an option to show POI of a certain group (for example gas stations) *along the route* (say +- n km/mi, optional value). That should not be a dynamic option but a 'display GROUP (select) along the current route' button, which helps identify a POI (or multiple) to add as via point (or mark as 'visible') and then hide everything else again.
@zhaelon - interesting post. Your suggestion above is not quite the same as my existing help topic (http://help.locusmap.eu/topic/show-nearest-points-along-current-navigation-track) but you still may like to vote for it. Currently 12 votes.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 29, 2017, 14:21:34
*** BETA version 3.25.5.3 ***

I believe that Route planner is now close to what I can imagine as first usable public version.

@zhaelon: thanks for a complex feedback. Faster access to content ( mainly points ) is something a) I'm surprised that more people does not want, b) is something I'm aware of and that definitely will be improved, but not as the first iteration of Route planner.
Current workaround is to close planner, change what is needed and return back. Two clicks more, not a big problem for now I believe.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Žajdlík Josef on September 29, 2017, 23:00:28
BETA version 3.25.5.3
The new NOGO points with the option of setting the validity and the diameter of the circle are much better. However, I would ask for the possibility of setting a smaller diameter, ideally 15 m. This would be enough for most roads and would not overlap with other roads like SCR NOGO.jpg
There are still minor translation errors. Automatically added commands are in English. EN. But if I add the command manually, then it appears in Czech, see. CZ.

CZ:
Nové NOGO body s možností nastavení platnosti a průměru kružnice jsou mnohem lepší. Poprosil bych ale o možnost nastavení menšího průměru, ideálně tak 15 m. To by mělo stačit na většinu silnic a nepřekrývalo by to další cesty jako u SCR NOGO.jpg
Ještě jsou menší chyby v překladu. Automaticky přidané příkazy jsou v angličtině, viz. EN. Pokud ale přidám příkaz ručně, pak se zobrazuje česky, viz. CZ.

(https://s26.postimg.org/5nw8erfn9/kruh_nogo.jpg) (https://postimg.org/image/5nw8erfn9/)

(https://s26.postimg.org/q5h6qerqt/image.jpg) (https://postimg.org/image/q5h6qerqt/)

(https://s26.postimg.org/zejd0j0mt/image.jpg) (https://postimg.org/image/zejd0j0mt/)


Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on September 30, 2017, 00:27:08
Thanks for suggestions Andrew. I'll look on texts a lot lot deeper next week with Michal.

And recompute ... ah I made a small gift for you just for testing for now and forget to mention. Try to long-click on big blue "choose source" icon in bottom left. Hope it is enabled in Beta :).
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on September 30, 2017, 00:38:21
*** BETA version 3.25.5.3 *** @zhaelon: <snip> a) I'm surprised that more people does not want
+1

3.25.5.3 - wow excellent NOGO functionality.

1) I still observe when a NOGO is deleted the track segment is not recomputed. See also my point #3.

2) I like the new item description "Part <N> of plan" when track segment is selected. However I think there is potential confusion between track point and track segment (part N). For example if I tap track segment, popup says multiple items, I tap "Part 1 of plan" but then next popup says "Trackpoint". So user is confused - did I just select a track point or part 1? And what is the difference? Is there a track point? Tap anywhere along a track segment/ part and you get the same point. Maybe replace "Trackpoint" popup with "Part <N>"?

3) I still can't force manual recompute of a track segment or whole route. How do you suggest I recompute track if I chose a different profile?

I would really like to use the new Route Planner instead of external BRouter method - http://docs.locusmap.eu/doku.php?id=manual:user_guide:tracks:planning:brouter but until manual recompute after selection of BRouter profile is possible then it is still too many taps. I still suggest two menu items: A) Trackpoint popup > Recompute, and B) Tools menu > Recompute all.

4) If I tap 10mm away from a Nav point along track, I want to display "Trackpoint" popup, but I never get option, the Nav point pop is always displayed. Shouldn't a "Selected items" listing <Nav point> and "Part <N>" be displayed?

5) "Selected items" popup should be renamed "Select an item".

6) Existing track > Route Planner > Tools > Save Plan. I have now saved this plan as a copy of original track. How do I modify existing track, not saving a copy? If I save with same name, I get two tracks (existing/ new) with same name.

7) Existing track > Route Planner > modify, for example add Shaping point > Back button > Route Planner > Shaping point is lost. Is this a bug?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on September 30, 2017, 09:24:42
Quote
And recompute .... Try to long-click on big blue "choose source" icon in bottom left
perfect thanks :)
Quote
I would ask for the possibility of setting a smaller diameter, ideally 15 m.
+1

set a nogo point valid for the currend day isn´t possible :-[
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: T-mo on September 30, 2017, 11:45:06
 BETA version 3.25.5.3
 route planner:edit: changed to unordered list-style
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on September 30, 2017, 12:04:03
Quote
And recompute .... Try to long-click on big blue "choose source" icon in bottom left
@balloni55 - thank you! I must have missed that comment. Not as intuitive as menu item, but good enough for me now I know the secret.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on September 30, 2017, 12:10:30
BETA version 3.25.5.3
 route planner:
    while moving the map I accidentally moved a red point, very sensitive..maybe adding some touch-
@T-mo - use the Undo button (top left arrow) if you accidentally move a red point

Tools > Travel time: there are no profiles for cars, even though I planned the route with a car-profile. I would like to define some profiles (fast, eco,..) just to get an idea. Of course traffic can change a lot, but as a first approach it would be nice
@T-mo - I suggested similar 9 months ago - only 3 votes - http://help.locusmap.eu/topic/provide-vehicle-types-for-travel-time-calculation - please vote for my suggestion. Seems crazy to me there is BRouter profile for car but can't calculate travel time.[/list]
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: lor74cas on September 30, 2017, 20:08:09
Hello
I tested the very good job you did with route planner.
I noticed that fast car with locus profile avoids motorway but I have nothing checked in the avoid options, but the positive and negative gain are correct.
With brouter profile fast car the route use motorway but positive and negative gain goes crazy.  I think it's due to the high number of tunnel in this case the gain is of the above mountain.

If you clear then route the nogo points are not cleared so you need to find them on the map and delete one by one.

I think that can also be helpful if we can move nogo points.

Inviato dal mio SM-G800F utilizzando Tapatalk

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on September 30, 2017, 23:49:21
And recompute ... ah I made a small gift for you just for testing for now and forget to mention. Try to long-click on big blue "choose source" icon in bottom left. Hope it is enabled in Beta :).
@menion - beautiful gift - thank you.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: 0709 on October 01, 2017, 10:28:40
The new Planning tool.

A: Need track snap to road, caused by fast tap unprecise refpoint position actions. (Quick Point)

B: Actual Planning: Create Shaping Point is Fast.  Create (standard) Via Point is Slow(er).
Previous version(s): First tap Shaping Point. Next tap (at same position) Via Point.

         

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on October 01, 2017, 18:01:58
@Žajdlík Josef:
- understand, let's try it with 25m.
- about translations: well probably side effect of work-in-progress

@Andrew Heard:
#160:
1), 3) ... I still do not know how to handle it correctly, so as you already know, temporary solution over "long click".
2) hmm you are correct. Number of trackpoint within a segment is not necessary I believe, but information that this is a certain trackpoint within a track is. And it is not clear from simple "Part <N>". So what about simply "Point from part N"?
4) I expect here that in most cases you (as an user) will want to deal with these special points, not directly with trackpoints. So in case, via-point or shaping point are the only interesting points under clicked place, they are immediately selected instead of choice. There is always option to zoom in more to select required trackpoint more precisely.
5) thanks, make sense
6) again for my surprise, no one complains till now :). I was thinking about dialog with simple options "Overwrite" or "Save as new". 
7) it is important to keep in mind, that route planner is made of planning of new route. If you on existing track tap on "Route planner", track is loaded to planner, but there is no connection to original track! This should be solved by point 6), but I'm really worried to save changes immediately to original track.

@balloni55:
hmm today is first of October ... damn, another year with Locus passed :). Anyway if you set validity of Nogo point to 1. 10. it is more common that this 1. 10. point will be still valid right? Consider as fixed.

@T-mo:
- notification on nogo placed near shaping point: well, not sure how to deal with it for now anyway notification is not ideal here I think. It is usually clearly visible where nogo was placed and that cover also existing shaping point.
- syntax with T: ignore it, "T:" means feature feature in progress
- Tools > statistics >show chart : good point, I always forget to solve it, thanks. Unfortunately I have no simple solution here for now, so best to hide this icon for now.
- list of shaping points: really hope this is not necessary
- travel times: yep, there are made mainly for hike & bike without possibility to edit, for now

@lor74cas:
"fast car with Locus profile" means? :). And yes, tunnels cause troubles, because Locus compute elevation on the surface of terrain. Quite hard problem for now ...

@0709:
- snap to road: hmm ... how to simply do it? Unfortunately there is still no interaction with underlying map.
- fast change shaping > via-points: you are right, in previous old version, tap on shaping point caused change to via-point. But now, it is also needed to offer change of location and option to delete it, so simple tap is not useful here, hmm.
To be true, I'm still not convinced that Via-points are needed to be used so often! I still consider them as points, that I really wants to visit and that I wants to be notified about. Such points are quite rare compare to shaping points, aren't they? Also, when you create new point from existing point on map, it is already created as "via point", so it save some time.
So my final decision for now: faster creating of via-points is not needed. I'll anyway see when Route planner will be used by less skilled users ;).
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: 0709 on October 01, 2017, 18:25:19
snap to road: Unfortunately there is still no interaction with underlying map.
As track design by (B) router offline near Shaping Points is +/- similar to trackrecord from "intoxicated" driver.

Do not like Via Points functionality anymore ?
Navigate by autorecalculate to Point makes no sense if your track does not contain at least one or multiple medium Via/info Points.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: balloni55 on October 01, 2017, 19:22:07
some nogo behavior is really a NOGO ;)
1. for test i added a few  nogo points while planing a route and saved this route.
Starting to my geocache tour i open a listing and select "navigate to".
After a while i wondered why i am not guided the nearest/fastest route to my target. :-[
Now i noticed that each  "nogo point" inside any saved route is aktivated/considered :-\

2. nogo points created with "Quick point" and store it to point folder are also considered while "Navigate to" although this nogo point is hidden :o
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on October 01, 2017, 19:25:21
@0709:
It is really not technically possible to do offline some road-snapping.

Do not like Via Points functionality anymore? ... don't get me wrong. I love via-points and I find them super useful!! I only wanted mention, that even during my field testing during vacation, I found that usage of these points should be mainly for really important and interesting places that I want to know about during ride. So I expect, there will be usually a lot less via-points in finished route plan then basic shaping points, that's all.

Navigate by autorecalculate to Point makes no sense if your track does not contain at least one or multiple medium Via/info Points.... in case you plan round trip, then yes of course.

@balloni55:
1. nogo points are globally defined for a whole Locus ( so Route planner & real navigation ). They are not sticked to planner route only. Effect is same as when you used (old system) NOGOXX named points before.
2. I have absolutely no control over this, you have to write Arndt because of this. Anyway I believe that this weird system won't be no longer needed.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Žajdlík Josef on October 01, 2017, 20:32:03
Perceptions of using NOGO points.
1) The "ignore NOGO" option should be added to the route planning menu. This option would also be saved with the route. The point is that NOGO will be used mainly where you can not go by car or bike. However, if I plan a hiking trail, I can go through the NOGO areas through the pavement.
2) It would be good to add a "show NOGO" option to the "Quick Settings" option. It would be good for driving when I do not navigate, but I would like to avoid the streets. Similarly, it would be useful to control NOGO, which should already be removed.

CZ:
1) hodilo by se do menu plánování trasy přidat volbu "ignorovat NOGO". Tato volba by se ukládala i s trasou. Jde o to, že NOGO se budu používat hlavně tam, kde nelze projet třeba autem nebo na kole. Pokud ale plánuji trasu pro turistiku, mohu oblastmi s NOGO body projít třeba po chodníku.
2) bylo by dobré třeba do "rychlých nastavení" přidat možnost "zobrazit NOGO" Hodilo by se to za jízdy když nejedu podle navigace, ale přesto bych se chtěl vyhnout neprůjedným ulicím. Stejně tak by to využitelné pro kontrolu NOGO, které už by bylo vhodné odstranit.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on October 02, 2017, 01:55:09
@Žajdlík Josef:
- understand, let's try it with 25m.
+1

@Andrew Heard:
2) hmm you are correct. <snip> So what about simply "Point from part N"?
+1

@Andrew Heard:
6) again for my surprise, no one complains till now :). I was thinking about dialog with simple options "Overwrite" or "Save as new". 
7) it is important to keep in mind, that route planner is made of planning of new route. If you on existing track tap on "Route planner", track is loaded to planner, but there is no connection to original track! This should be solved by point 6), but I'm really worried to save changes immediately to original track.
Menu > Route Planner > create new route... of course. But track > Route Planner > edit existing route > ("Save" > "yes|no") | "Save as new".  This is behavior of RWGPS system too.

I still question this sequence:
I still think add NOGO should have undo. And Delete NOGO should force auto recalc. It won't be obvious to a user to long-tap the Compute Source icon for Recalc All.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: 0709 on October 02, 2017, 10:21:11
Shaping Point(s) into exported gpx ?
As ONLY Locus must recognise/reconstruct.
Shaping Point indicator in trkpt attribute <type>
<trkpt lat="51.0529732704163" lon="3.99975299835205">
<type>Shape</type>
</trkpt>
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on October 02, 2017, 15:55:34
@Žajdlík Josef,
1) not so easy here to satisfy all options. Best should be probably define in every Nogo point it's validity to car/bike/foot based profiles. Then you should define it as nogo for car & bike and allow it for foot automatically.
2) (something to better handle them) later ;)

Other problems/questions/ideas related to no-go areas was probably already few times discussed. As I mentioned before, no-go areas won't be in next public version yet. I keep in mind all feedback, thanks for it, but no more changes around no-go areas will be implemented to next version(s) for now, sorry.

I need gather some more feedback from other, less skilled users + probably do one more usability testing that we from time to time do in our office on real users that usually never heard about Locus Map. Thanks for understanding.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: lor74cas on October 02, 2017, 18:41:24
Hello,
This is what I mean with Locus or brouter profile(https://uploads.tapatalk-cdn.com/20171002/8266c299125416b7cc5e5aa465be9099.jpg)(https://uploads.tapatalk-cdn.com/20171002/c34782d5311870ce999fa0ada35cd9b5.jpg)

Inviato dal mio SM-G800F utilizzando Tapatalk

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: poutnikl on October 02, 2017, 19:34:11
Perceptions of using NOGO points.
1) The "ignore NOGO" option should be added to the route planning menu. This option would also be saved with the route. The point is that NOGO will be used mainly where you can not go by car or bike. However, if I plan a hiking trail, I can go through the NOGO areas through the pavement.

Note that the original BRouter nogo system can activate nogos separately for each profile, resp. transportation mode. E.g. all nogos for cars, some for bikes, none for pedestrians.
And yes, they are considered globally, so not limited to a particular route.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: LocusUser#1 on October 02, 2017, 20:09:27
Last Beta, new "Modify track" editor

1. The tool button (in the red circle) has no function.

2. For what we need the function jump to the gps position (in the green circle). For me the function is superfluous.

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: lor74cas on October 02, 2017, 20:13:22
Perceptions of using NOGO points.
1) The "ignore NOGO" option should be added to the route planning menu. This option would also be saved with the route. The point is that NOGO will be used mainly where you can not go by car or bike. However, if I plan a hiking trail, I can go through the NOGO areas through the pavement.

Note that the original BRouter nogo system can activate nogos separately for each profile, resp. transportation mode. E.g. all nogos for cars, some for bikes, none for pedestrians.
And yes, they are considered globally, so not limited to a particular route.
IMHO when I use the clear route button if I have a pop up to choose to: clear all nogo/profile nogo/current visible nogo points or something similar should be helpful.
I used the nogo points to avoid some sections of a track for a hike but next time  I do not want the nogo still there and to give them all an expieration of a week is tedious.


Inviato dal mio SM-G800F utilizzando Tapatalk

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: poutnikl on October 02, 2017, 21:16:46
IMHO when I use the clear route button if I have a pop up to choose to: clear all nogo/profile nogo/current visible nogo points or something similar should be helpful.
I used the nogo points to avoid some sections of a track for a hike but next time  I do not want the nogo still there and to give them all an expieration of a week is tedious.

I do not agree with Arndt - the BRouter author - on nogo usage philosophy. IMHO, nogo points should serve as really nogo points, permanent(e.g. really bad road or always traffic jams or whatever) or temporary ( e.g. road fixing).  They should not be used as "negative viapoints/shapepoints".
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: lor74cas on October 02, 2017, 22:25:08
IMHO when I use the clear route button if I have a pop up to choose to: clear all nogo/profile nogo/current visible nogo points or something similar should be helpful.
I used the nogo points to avoid some sections of a track for a hike but next time  I do not want the nogo still there and to give them all an expieration of a week is tedious.

I do not agree with Arndt - the BRouter author - on nogo usage philosophy. IMHO, nogo points should serve as really nogo points, permanent(e.g. really bad road or always traffic jams or whatever) or temporary ( e.g. road fixing).  They should not be used as "negative viapoints/shapepoints".
Sometimes I'm so lazy that I prefer to give just two points, start and end, so I use nogo to block the route on unwanted trails.
I don't know what is the main purpose of nogo points, this is the use sometimes I made of them. So if we can use nogo also in this way why don't give them a more user friendly menu to clear them after use?

Inviato dal mio SM-G800F utilizzando Tapatalk

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: john_percy on October 02, 2017, 22:41:52
If there is more than one way to use no-gos, surely we need options to use them in those different ways.
I should not design an app so that everyone has to do it my way!

Sent from my XT1039 using Tapatalk

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on October 02, 2017, 23:30:14
Shaping Point(s) into exported gpx ?
As ONLY Locus must recognise/reconstruct.
Shaping Point indicator in trkpt attribute <type>
<trkpt lat="51.0529732704163" lon="3.99975299835205">
<type>Shape</type>
</trkpt>
+1 = would allow round trip GPX export/ import of route plan
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on October 02, 2017, 23:33:53
They should not be used as "negative viapoints/shapepoints".
I sometimes find nogo's very convenient for negative viapoints/shapepoints. Sometimes it is the fastest method for shaping my route.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on October 03, 2017, 08:47:01
@lor74cas:
 ah understand, thanks. Internal Locus profiles are made @pountikl but are already quite old. Seems I'll have to update it.

@LocusUser#1:
1) just yesterday morning I've removed it ;)
2) good point, I'll think about it and probably remove as well, thanks

Nogo usage:
- here comes good question that will define UX around nogos. What is a main purpose of these areas? I was always working on it with single idea in mind: define area, where is any problem so I wants to avoid it. Exactly as wrote Libor here (http://forum.locusmap.eu/index.php?topic=5827.msg49093#msg49093) .
I never thought about them as about tool that should "shape" an planner route. And to be true, I still see no reason for this. Because I expect that planner will mostly me used really for planning, one or two clicks more for additional shaping points, does not look like a problem.

So for now:

Feel free to discuss about them, but it is not a priority for me for now and I'm personally still not sure how to deal with this feature, so consider current state as some "Alpha version", thanks for understanding.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on October 03, 2017, 11:13:30
I never thought about them as about tool that should "shape" an planner route. And to be true, I still see no reason for this.
Often BRouter needs no encouragement but sometimes I encourage the chosen route with a Shaping point, sometimes with a NOGO area. Each has it's use and advantage depending on the characteristics of the current route. Generally for me a NOGO is only needed for the life of the route. No longer. As my cycle touring is always to a new area.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on October 03, 2017, 11:15:31
In this case, permanent nogo areas also cause no problems to you, right? And with some default validity value set to for example 14 days since create, it solve also automatic clear of old areas, hmm?  ;)
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on October 03, 2017, 11:25:13
No problems for me; either way. I only reply to your comment "I see no reason..." with my reason :)

Just a general comment:- Until now I have used the "external BRouter" method of route planning - http://docs.locusmap.eu/doku.php?id=manual:user_guide:tracks:planning:brouter. I can quickly generate X routes for X profiles, then compare & contrast. But now, finally, the new Route Planner has overtaken this method for convenience. With Shaping points & NOGO areas it just gets better & better.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: poutnikl on October 03, 2017, 11:38:01
They should not be used as "negative viapoints/shapepoints".
I sometimes find nogo's very convenient for negative viapoints/shapepoints. Sometimes it is the fastest method for shaping my route.
I mean - description of what I want is easier by expressing what I want, not by what I do not want. If I would try to order my dinner by nogo approach.....

The admitted advantage of nogos for route shaping is that it bypasses eventual viapoint count restrictions. Personally I prefer to use the profile that follows my priorities and eventually I choose viapoints that I do want visit or go through.

It not at all about users should act this way, I am just describing my way. That is all.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: poutnikl on October 03, 2017, 11:53:15
Generally for me a NOGO is only needed for the life of the route. No longer. As my cycle touring is always to a new area.

I see. But imagine everyday bicycle commuting in big cities with regular municipal announcements about short and long term road closures. There is even Android application to monitor them for my country. They are often not updated in OSM, or with delays, or routers generally do not deal well with time restrictions.

I have a nogo folder in Locus and put their nogos there with target date in name, periodically purging them.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Žajdlík Josef on October 03, 2017, 12:43:48
It would also be possible to make NOGO points as sets. One set would be cycling, another for hiking. Selecting a set-up for a route outside the route planner could then be solved using presets, and NOGO could also appear on the screen while driving.

CZ: Bylo by taky možné udělat NOGO body jako sady. Jednu sadu bych pak měl třeba na cyklistiku, jinou pro turistiku. Výběr sady pro výpočet mimo plánovač tras by se pak mohl řešit pomocí presetů, NOGO by se taky mohly ukazovat na obrazovce za jízdy.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on October 04, 2017, 00:58:44
But imagine everyday bicycle commuting in big cities with regular municipal announcements about short and long term road closures.
@poutnikl - yes of course.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on October 04, 2017, 18:42:49
New Beta version 3.25.5.5 just uploaded. Enjoy it.
Also because of new problems with Dropbox, I'm thinking about publishing new version with updated Route planner & Track editor next week. Few last days to stop me ;).

EDIT: ah, incorrectly inserted list of news, so here is it:
chg: huge number of changes in Route planner and track editor. Polished UI, texts, functionality
chg: completely removed old "Add new route" and "Track editor". No way back...
fix: not working Dropbox support
fix: crash when sharing export track on Android 8.0
fix: not working language switch on Xiaomi devices
fix: disabled store permanently for navigation does not work correctly ( http://help.locusmap.eu/topic/if-navigate-to-route-is-recalculated-the-store-permanently-setting-is-ignored-route-is-permanent )
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: lor74cas on October 04, 2017, 22:44:48
Why do not add import function to the pop up window of + icon in data manager instead to search it in the top right corner on the ... icon ?(https://uploads.tapatalk-cdn.com/20171004/8200dc7cc54e54ed3162c0235d599194.jpg)

Inviato dal mio SM-G800F utilizzando Tapatalk

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on October 05, 2017, 07:01:12
Good point, thanks!
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: 0709 on October 05, 2017, 09:43:06
http://help.locusmap.eu/topic/convert-to-navigation-waypoint-edit-this-waypoint
Locus 3.25.5 (no pc): Create Info Point is possible, but is a complex so slow process.
Faster by (single tap) "Point" menu ?
Point:
=> Delete
=> Move
=>To Trackpoint
=>To Shaping Point
=>To Navigation Point => SELECT Navigation Icon => SAVE
=>To Via Point => EDIT name => SAVE
=>To Info Point => EDIT name => EDIT description => SELECT Garmin/Locus Icon => SAVE
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on October 05, 2017, 11:14:34
New Beta version 3.25.5.5 just uploaded. Enjoy it.
chg: huge number of changes in Route planner
@menion - huge change from 3.25.5.2? really? what to test?

Until now I haven't tested the Track Editor. For me not needed much with Route Planner. But a question: if I move to first or last track point in the Track Editor does it make sense for Tools > Insert break menu item to be enabled? A break can only be inserted when an intermediate point is selected?

Track Editor > Tools > "Tuto, remove"
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Shara97 on October 05, 2017, 12:01:01
hello, my name is shara, i'm italian girl and sorry for my language  ;-)
I have install first time locus for a week
i have nexus 5x and android 8 Oreo
pc windows 8.1
my question's:
1) to know my version where I have to look?

2) one problem is share track, but I saw that it was solved with new version..good
but i have another problem: if I save the track (example in the export folder...), if i connect the nexus of the Pc
in the Locus/export folder I can not find the gpx file...I have to restart nexus, for find the file..
(is the problem locus? or android, nexus, pc..?

3) the version in this post is beta...where then I find the  stable version ?
 and for update version, first best to uninstall actual version? but the folder locus/map are you lost?
(i have several maps GB in this folder..)

thanks shara

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: lor74cas on October 05, 2017, 12:38:55
hello, my name is shara, i'm italian girl and sorry for my language  ;-)
I have install first time locus for a week
i have nexus 5x and android 8 Oreo
pc windows 8.1
my question's:
1) to know my version where I have to look?

2) one problem is share track, but I saw that it was solved with new version..good
but i have another problem: if I save the track (example in the export folder...), if i connect the nexus of the Pc
in the Locus/export folder I can not find the gpx file...I have to restart nexus, for find the file..
(is the problem locus? or android, nexus, pc..?

3) the version in this post is beta...where then I find the  stable version ?
 and for update version, first best to uninstall actual version? but the folder locus/map are you lost?
(i have several maps GB in this folder..)

thanks shara
Answered in PM in Italian
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: alezy on October 05, 2017, 12:44:29
@menion, some small ideas:
When I in Track Editor and press to any point, point menu is shown. The most used action is track modifying (Insert/edit trackpoint), so you may enable editing mode by long press to pencil. And also in top point info with (i) sign, you can show Details on long press. Also, why you disabled long press on "delete point" action to clear route?
In point detail screen it would be useful to have left/right swipes for showing next/previous point.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on October 05, 2017, 16:28:25
@0709:
not sure what you expect from me now.

@Andrew Heard:
I wrote huge list of changes ( smaller changes I thought ).
List? Hmm ... as I see in my source code repository, changes related to Route planner system:
- chg: completely new system of dynamic actions for move/zoom/fling actions and applied this system on few places
- chg: new system of centering map content  ( based on panning instead of direct set of new location )
- chg: disabled "map" button on chart displayed from Route planner
- chg: fixed validity of Nogo points to one day ( to be valid also for selected day )
- chg: performance improvements
- chg: removed old Route planner system
- chg: convert trackpoint > shaping point does not trigger recalculate
- chg: improved internal handling of nogo places
- chg: text improvements

"Insert/remove break" .. bug, thanks

@alezy:
Insert/edit trackpoint action is maybe most used Your function, but for sure not to every user. No long click is currently planner, sorry.

"Also, why you disabled long press on "delete point" action to clear route?" - you mean in Route planner, right? Clear of route is currently placed in side menu. It's usage is not so often so one slide to open menu to access this feature is for sure not a problem.
"Left/right" swipes ... yes, that should be nice. I know I've read this idea a long time ago on help desk, cannot find it now. Anyway it's not an easy task for now, sorry.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: zhaelon on October 05, 2017, 16:37:04
I noticed that when you add a point from the database, say Restaurant A to the track with the + button, it becomes a via point and uses the name as description. When you move the point, it is converted back to a shaping point. This is a good feature, as it makes planning and shaping easier.

Maybe I missed it, but I was looking for the remaining option: moving a shaping point on top of / near a point from the database could offer the conversion to a via point. That way, I could plan a route, search for a place along the route, then add a shaping point near the POI and move it to the search result and directly have a via point with the additional information :-)

The fix for the Google Places works like a charm. I haven't seen any wrong entries starting with the previous beta. Thanks a lot!

I noticed one more thing during my tests: I planned the routes using the beta version, stored them and then use the pro version as usual (because I added the widget, etc) for track recording. This leads to the following behavior: If you start recording on the pro version  and open the beta, suddenly both are recording. And both use different pause / recording state at least they indicate this.. Is there a way to lock recording to only one of the two instances? ;-)

Sadly my motorcycle vacation is almost over, so I won't be able to do a lot more testing.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on October 05, 2017, 22:09:15
Hello, thanks for a feedback.
I have to ask, why you would like to create via-points by moving shaping points closer to existing points? Why not to directly tap on existing point and add it to plan?

Google Places fix: thanks for testing and confirmation!

Hmm using both versions at once is really not recommended. It may lead to unexpected problems like these you wrote about. No simple solution on this, sorry.

Hope you had a nice time!
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: john_percy on October 05, 2017, 22:17:51
The advantage of installing both versions at once is that when the beta expires and reverts to locus free functionality you can use the pro version until the next beta comes out.

Sent from my XT1039 using Tapatalk

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on October 05, 2017, 23:30:05
@john_percy - I think issue is running Pro/Beta simultaneously (agree sounds like bad idea) rather than just installing both.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: lor74cas on October 06, 2017, 07:26:25
Route planner


dragging the points often is very difficult, sometimes dragging occurs when unwanted. More usable is moving the points by modify menu and using pick on the map.
For me dragging is not convenient and produces more errors than results.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on October 06, 2017, 08:06:51
@john_percy:
yep, it was about "running" both at once as Andrew wrote. Both versions on device installed should be no problem.

@lor74cas:
what is main ( and more often ) problem here? Tap not too close to point, so it is not moving? Unwanted move instead of scroll of map? Are you playing with Route planner at home or outside during activity? How you imagine it should work, tap on point > edit > grid with options > and as result, moved point? So no dragging?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: lor74cas on October 06, 2017, 08:24:18

@menion:

what is main ( and more often ) problem here?
unwanted drag or missing dragging in the same way

Tap not too close to point, so it is not moving?
usually not but sometimes moving the map does it by accident

 Unwanted move instead of scroll of map?
yes
 Are you playing with Route planner at home or outside during activity?
At home, but with gps fix most ot time
 How you imagine it should work, tap on point > edit > grid with options > and as result, moved point? So no dragging?
Yes, this sequence always works and does not create problems, but this is my experience with the small screen of my device. I do not know if other beta testers had any problems with dragging.

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Andrew Heard on October 06, 2017, 11:15:37
I do not know if other beta testers had any problems with dragging. [/b]
@lor74cas - I mostly use tap > Edit position rather than drag but drag does have advantage of quickly creating a Shaping point. If I drag by accident just tap the Undo button. Seems like good compromise to me.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Shara97 on October 06, 2017, 11:26:45

Answered in PM in Italian

thanks lor ;-)
shara
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: lor74cas on October 06, 2017, 12:45:45
I do not know if other beta testers had any problems with dragging. [/b]
@lor74cas - I mostly use tap > Edit position rather than drag but drag does have advantage of quickly creating a Shaping point. If I drag by accident just tap the Undo button. Seems like good compromise to me.
Dragging a point is very difficult on my small screen, but I have many unwanted drags. Dragging, to me, only works when I do not need it  >:(
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: matmas on October 06, 2017, 13:59:34
I love dragging and it works fine and fast most of the times

Inviato dal mio SM-G930F utilizzando Tapatalk

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on October 06, 2017, 15:41:18
Quite surprising @lor74cas. I'm from time to time test Locus Map on older SGS2!! so did it now just for sure and all is absolutely fluent and perfectly working ( Route planner ). So personally do not see big problem here. I'm aware that problem may comes on new but less powerful phones.
I'm anyway sorry, for now dragging is a core feature and definitely can't be simply disabled. We may think about some "planning without dragging mode", enabled over settings, that should allow to control these points over "edit" button and disable also drag feature. For this, I'll anyway need topic on help desk & few more votes to be sure, it's not just a "one-men problem". Thanks for understanding.
Btw. suggest to improve app performance little bit: http://docs.locusmap.eu/doku.php?id=manual:faq:locus_performance , it should help here!
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: lor74cas on October 06, 2017, 17:07:35
Quite surprising @lor74cas. I'm from time to time test Locus Map on older SGS2!! so did it now just for sure and all is absolutely fluent and perfectly working ( Route planner ). So personally do not see big problem here. I'm aware that problem may comes on new but less powerful phones.
I'm anyway sorry, for now dragging is a core feature and definitely can't be simply disabled. We may think about some "planning without dragging mode", enabled over settings, that should allow to control these points over "edit" button and disable also drag feature. For this, I'll anyway need topic on help desk & few more votes to be sure, it's not just a "one-men problem". Thanks for understanding.
Btw. suggest to improve app performance little bit: http://docs.locusmap.eu/doku.php?id=manual:faq:locus_performance , it should help here!
Don't worry about it I just reported my troubles in drag experience, you created the undo feature so I can always correct errors.
I agree, Let's wait the response when the beta will become main version from help desk.

Inviato dal mio SM-G800F utilizzando Tapatalk

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: 0709 on October 06, 2017, 17:11:41
Is absolutely fluent and perfectly working ( Route planner ).
Fluent ?  Video example ?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: zhaelon on October 07, 2017, 21:59:51
Hello, thanks for a feedback.
I have to ask, why you would like to create via-points by moving shaping points closer to existing points? Why not to directly tap on existing point and add it to plan?

Google Places fix: thanks for testing and confirmation!

Hmm using both versions at once is really not recommended. It may lead to unexpected problems like these you wrote about. No simple solution on this, sorry.

Hope you had a nice time!

The reason is probably the way I plan motorcycle tours: I first construct the rough plan (start, POI, end) and then search for things to enhance the tour (interesting roads, landmarks,...) and modify the route accordingly. Then I search for specific POI along this route, for example a resting area, picnic places, restaurants, gas stations, etc and modify the route again.

And here I would like to just move a shaping point to an existing point,for example by moving the red dot (middle of a segment) to the via point. With the add option of the point, I would need to specify where to insert the point, which is not necessarily the beginning or end (or second last) point.

For the other problem: I just wanted to let you know that while both free and pro can be installed side by side, having a track recording active and accidentally opening the other version leads to both trying to record. I noticed only while beta testing and was surprised, that was all :-)

The motorcycle vacation was awesome and for me, Locus plays a huge part in it (planning, recording, etc). So I would like to thank you again for your efforts and hope that you still enjoy working on it!
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on October 07, 2017, 23:55:17
@0709:
you wants to record a video how Locus Map works on SGS2? Oki, I'll do something short ...

@zhaelon:
moving with red points is really useful and quick ... sometimes. In case, you are far from nearest visible points, it is a pain! For this "+" button of points has three options, not just start and end of track. But also "nearest", which should really place selected point to nearest possible place in route. So planning should be really simple. You setup route by shaping points and interesting points along route you may simply add later by this third option.

And yes, for my own surprise, I still like what I do ... I believe that huge part on it has a nice and useful feedback from you and others here on forum and help desk. I'm also a little workaholic with sense for detail and head full of ideas, and too slow fingers to implement everything .. terrible combination :).
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: 0709 on October 09, 2017, 08:53:06
Quote
I do not know if other beta testers had any problems with dragging. [/b]
Yes.
Quote
Dragging a point is very difficult on my (small )screen, but I have many unwanted drags. Dragging, to me, only works when I do not need it  >:(
  Agree.
Quote
So no dragging?
Only reliable secure method is by edit menu. Different hardware, different experience ?
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: tommi on October 09, 2017, 15:05:08
New route planner: track width is 3px if I enter the planner. I change it to eg 6px as this is the width I'd like to see. When I enter the planner for the next time width is back to 3px again. How can I reliably store my setting if 6px?

Gesendet von meinem SM-G930F mit Tapatalk

Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: Žajdlík Josef on October 09, 2017, 19:52:34
The latest beta version does not work for export to Openstreetmap. The Pro version is normal. Beta version reports Unautorized even when login to your account is OK.

CZ: V poslední beta verzi nefunguje export do Openstreetmap. Ve verzi Pro jde normálně. V beta verzi hlásí Unautorized i když přihlášení do účtu je v pořádku.
Title: Re: [APP] - version 3.25.+ ( 9. 8. 2017 )
Post by: menion on October 11, 2017, 14:12:19
Hi guys,
some new problems with Dropbox forced me to speed up release of a new version little bit.
So I'm glad that after quite long time of testing, new version with new Route planner & Track editor is published. Thanks all for a big help with this task!

Problem with editing of track by dragging is big surprise for me. I'm still not sure how to deal with it to be true ...

@tommi:
default width parameter is globally defined in settings > maps > points & tracks > track width

@Žajdlík Josef:
thanks! fixed

And never-ending work continue, so let's look into the future (http://forum.locusmap.eu/index.php?topic=5916) ...