Locus Map - forum

Development => Versions => Topic started by: menion on April 15, 2020, 14:07:36

Title: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on April 15, 2020, 14:07:36
Important links
- list of news (https://help.locusmap.eu/announcement/version-3-45-15-4-2020) of public versions

Versions
15. 4. 2020 - Locus 3.45.0
23. 4. 2020 - Locus 3.45.1
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: tapio on April 16, 2020, 05:41:51
Thanks for the new version, you worked very hard. Can you remove the "active profiles" limitation at some point? E. g., I'd rather display like 6 hiking profiles, but the icons can be misleading, because they are static. I refer to - see attachment.

I also was wondering if a more direct access to the routing profiles would be nice. Currently we have to assign them to a button first, a bit of a static approach. Maybe something like an additional dropdown with profiles to pick from, for the routing profile power users... Especially in "recalculate all" I think it is nice to have.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on April 16, 2020, 08:44:54
Hi tapio
there is a big problem with setup of profiles. It comes from history and also from the united system across all routing systems in the app. All profiles have to have unique identification that is hardcoded in the application so it cannot be dynamic (like that user say "I want six hiking profiles").

So it is doable, I was also thinking about it and like this idea (to be simply able to define own routing profiles like for example "Presets"), but it is quite a lot of work ... so later ;).
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: poutnikl on April 16, 2020, 09:56:19
...there is a big problem with setup of profiles. It comes from history and also from the united system across all routing systems in the app. All profiles have to have unique identification that is hardcoded in the application so it cannot be dynamic (like that user say "I want six hiking profiles")....

What about just implement the profile icon assigning/resetting ?
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on April 16, 2020, 10:00:46
Every ID has definition if it's hike/bike/car category => based on this, some other parameters are used, like compute of time estimates etc. As I wrote ... it's not so simple :)

Really, I was already thinking about it and I can't simply change the current system to allow bigger modification of BRouter profiles ... for now ;).
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: Henk van der Spek on April 18, 2020, 11:49:03
* fix: incorrect stop of navigation/guidance at the app exit, topic
This is not solved yet on Android 9. Version 3.45 still stays on in the background. Only closes fully after swiping up in the recent apps overview.

BUT: I did more testing and for me it now seems not related to an active guiding.
I have the same behaviour without an active guiding. If I only close Locus through the App itself (back button and confirm) even after 5 minutes Locus does the instant start. (The "sleeping" time is something like 10 seconds right?).
The behaviour is confirmed by the battery stats for the app: acitive 30 mins; backgroud 2 1/2 hours

I also tested all settings for Locus to bypass the screen unlock. Makes no difference. (Normally basic).
Also Locus as a service (normally off) makes no difference.

PS. in the topic I wrote about the active guiding as the probable cause but now I realise that only notified me of the problem through the beep sounding when we went off track too far.

PS2. The Motorola One got an update to Android 10 and the behaviour is exactly the same: Locus does not shut off unless I also "swipe up".
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: tapio on April 19, 2020, 15:06:59
If Audio channel is "Notification" and I want to change volume in <see attachment>, Locus instantly crashes.

BTW, I'd love to have Locus audio on the alarm channel, can you add this one? It's the most secure and predictable for me, because I do just alarm things/important audio there and I have Tasker keeping control over a useful volume level.

Background: Today I was a bit too optimistic relying on audio routing. There was no more voice and I thought "ok, just follow the path" and after 2km - in wrong direction - I recognized, media volume was set to zero. Most likely because there was accidental pressure on the phones volume knobs. The good part: the new route was lovely.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: slarti76 on April 20, 2020, 08:24:32
I'm not really sure what got improved about the two-finger measuring?!
The distance is still not better highlighted (eg. with a different background) and it's possible to get it hidden by the magnifier. See screenshot
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: freischneider on April 20, 2020, 09:34:19
I think the measurement is good.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: tapio on April 20, 2020, 11:00:12
I think the measurement is good.
Did you look at the screenshot of Slarti? It's not good.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on April 20, 2020, 15:00:37
@Henk van der Spek
weird problem with the closing of the app. Unfortunately, I have the only device with Android 10+ (Pixel 2) and there is no such problem > so little unsolvable for me for now.

I'm not 100% sure what changes I made in the recent version but I hope that issue with guidance beeping is really solved. Fact, that app is not perfectly closed is not a real problem, to be true, full-close of the app is weird (and generally not recommended) on Android. The problem should be in the case, such minimized app will still suck your battery (which I believe/hope does not happen).

Anyway, in the moment I notice same issue on my device (or I'll receive more similar bug-reports), I'll, of course, solve it somehow.

@tapio
you wrote "there was accidental pressure on the phones volume knobs" > app set one channel as active and when this app is active, volume controls control this channel! So in case, you choose "Alarm" channel, then volume up/down will control this channel so the problem will be the same.

I also did not have any crash when changing volume when "Notification" channel is active. The log will be needed here if you want to fix it.

@slarti76
distance text has a white border and arrows has a light white background. So on some dark maps, both should be better visible. Fact that value is hidden behind magnifier is another story. Value is simply put into center of the line and here is a result ...
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: 0709 on April 22, 2020, 19:15:42
Locus V 3.45
Report: POI alert problem
POI alert set: TTS - single alert - Distance trigger 100m
@ Navigation !  A SINGLE POI wpt in range is announced as "2 points in range".
UPDATE: 3.45.1 OK !
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: tapio on April 23, 2020, 16:22:19
SERIOUS. New stable version 3.45.1, it starts with an error message. I had to make a restore. From backup yesterday. After restore it works. Could be a problem on my end, database file broken? IDK. Didn't try restart because backup was new enough.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on April 24, 2020, 16:03:10
@0709
again ok with the latest version? Hmm ... :)

@tapio
well, hard to help here ... I'm glad you had a backup!
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: tapio on April 24, 2020, 18:42:24
Very good that Locus keeps the corupt db and names it accordingly.

I'm a backup junkie, so, cases of loss became increasingly rare over the last decades. The backup road is full of learning by pain.  ;D Most nasty thing is to realize after loss and after years, that you didn't include something important in the backup. Well, this is offtopic.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: balloni55 on April 24, 2020, 19:04:51
@ Petr
and how can user terminate subscription??
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: poutnikl on April 26, 2020, 17:51:15
ETA in route planner:

If I use BRouter bicycle profiles in the route planner, it is my understanding the stats bar uses the ETA ( estimated time of arrival ) provided by Brouter, or by some internal defaults.

But if I make LocusMap calculate ETA by ETA estimation from the planner menu, none of ETA estimation profiles fits the stats ETA.

I think it could be good to optionally allow binding a particular ETA estimation profile to a particular Locus transportation mode.

Eventual votes at https://help.locusmap.eu/topic/consistence-of-eta-in-the-route-planner


Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: 0709 on April 26, 2020, 18:54:35
ETA for the "universal person"  ?
Or a more optimal, so a realistic ETA expectation, by personalised Locus setting.
Suggestion: https://forum.locusmap.eu/index.php?topic=5953.msg49935#msg49935
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: poutnikl on April 26, 2020, 19:43:12
Well, the ideal case would be to be able to create and assign custom Route planner ETA profiles, tailored for your performance and various activities.

But as we do not live in an ideal world, for now just the Menion's predefined profiles from the Planner.

Note that I mean in this context just planned ETA, not the real time ETA on the road, but that should be obvious.

For now, I can observe the bicycle Router stats ETA fluctuates between fast and slow trekking ETA profiles. It would be better if you knew how it is calculated, no matter how good it fits your best fit.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: 0709 on April 26, 2020, 20:32:26
Quote
Note that I mean in this context just planned ETA
hmm...the suggestion is about the planned ETA (inclusive all expected arrivals onto the medium Via Points (for example a mountain top), of course only in Locus map. (Not by any external web source). So..to say the expected timespan ETA as generated in your personalised installed Locus

Quote
ETA (inclusive all expected arrivals onto the medium Via Points (for example a mountain top)

Time to next Via...
https://help.locusmap.eu/topic/timedistanceeta-to-next-via-point#comment-71695
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: poutnikl on April 26, 2020, 20:38:53


hmm...the suggestion is about planned ETA, of course only in Locus map..to say in your personal installed one.

I know it is, just not to confuse not involved users, as there was much of discussions about real time ETA.

I would prefer rather customizable than personal installation.



Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: poutnikl on April 26, 2020, 21:09:52
But customisation could do exactly that. Setting your own flat, climbing and descending speed rates, that may decrease over the time.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: Andrew Heard on April 27, 2020, 01:17:32
I *think* you are both in agreement! I agree too. Instead of the current 14 Estimated Travel Time profiles (track > More), none of which meet my requirements, it would be much better if a user could define their own. And for @0709 these could be updated over time to reflect "physics". I've always been curious (annoyed) why there is no car profile too, which is inconsistent with default routing profiles.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: voldapet on April 27, 2020, 09:44:44
@balloni55
thank you. You can cancel it anytime in the detail of the item in the Locus store. I updated the description of this item to improve it.
Thanks Petr
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on April 27, 2020, 09:52:56
Hi guys,

the best to start with a small explanation.

1. ETA visible directly in route planner
Compute ETA should match ETA computed during navigation (at least when navigation starts). It really internally start navigation feature in some kind of "simulation" and just compute time to target and finish it.

Here are two options:
- routing service supply times between navigation points, than app only sum these times
- or does not supply them, then Locus Map use average speed and distance. Speed is internally computed over time (1 hour block) for you based on activity in three categories: walk, cycle, car.

2. Time visible in "Compute trip" feature
In this case, it is a completely independent feature. Every profile has hardcoded a few parameters (more below). Use-case of this feature is to simulate real travel experience together with breaks on snacks etc.

Code: [Select]
        // basic horizontal speed in m/s
        var speed: Double = 1.0
        // speed to uphill (in vertical metres per hour)
        var speedUp: Double = 1.0
        // speed to downhill (in vertical metres per hour)
        var speedDown: Double = 1.0
        // container with breaks
        var breaks: Hashtable<Int, Int> = Hashtable()

So for example "Bike trekking easy" looks like:
Code: [Select]
        tripCycle1.speed = 14.0 / 3.6
        tripCycle1.speedUp = 500.0 / 3600
        tripCycle1.speedDown = 1000.0 / 3600
        tripCycle1.breaks[60 * 60] = 10 * 60
        tripCycle1.breaks[180 * 60] = 30 * 60
Among speeds, it also define 10 minutes break every 1 hour and 30 minutes big break every 3 hours.

Hope my explanation is clear.

Space for improvements I see:
- in case routing service return time, keep some kind of internal modification that modify even these time based on users real speed (discussed here on for maybe the year before)
- for "Compute trip" feature, allow to modify/create customized profiles
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: joeloc on April 28, 2020, 10:34:42
Locus exports/imports track color to gpx in a standard extension... and locus activity as custom locus extension. However, the rendering pattern and color (arrows, dots, whatever) is not exported/imported. Could you maybe make this work too?

I remember this working already at one point, that's why I post it here in the versions thread. But maybe I am mistaken, it's been a long time that I tried to import properly colored tracks with patterns.

Code: [Select]

<extensions>
<line xmlns="http://www.topografix.com/GPX/gpx_style/0/2">
<color>0D9B0D</color>
<opacity>0.83</opacity>
<width>8.0</width>
</line>
<locus:activity>cycling_mountain</locus:activity>
</extensions>
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: poutnikl on April 28, 2020, 10:52:28
@menion Thank you for the thorough explanation. I have approximately already understood what you have explained.

What I had in mind was, that for user convenience, the user could decide, what should be there.

 The summary ETA value on the stats bar could be

either as is now, as is or modified internally
either as the trip  ETA result from a chosen  particular ETA profile(built-in or custom),

It would have advantage of not to have to go there.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on April 28, 2020, 19:49:53
@0709
- invisible short segments > thanks, fixed
- recalculate all > hmm, may you give me a screenshot? Are you sure, it is an old track? Isn't it an alternative route provided by online GraphHopper in the Alpha version?

@joeloc
This never worked yet. I was already thinking about it, but because no global standard exists, I left it as is now. How you may use this? Just to share tracks from your Locus to other Locus instance right?
There is quite a lot of parameters, but I'll look at it ...

@poutnikl
This is definitely not a task for one evening ... I'm now little pushed by time to finish some less or more cosmetic improvements for LM4. Once it will be out, I really really wants to focus mainly on many incorrect algorithms on background so please remind me (again, sorry), this serious topic maybe half an year later. Thanks!
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: poutnikl on April 28, 2020, 20:16:23


@poutnikl
This is definitely not a task for one evening ... I'm now little pushed by time to finish some less or more cosmetic improvements for LM4. Once it will be out, I really really wants to focus mainly on many incorrect algorithms on background so please remind me (again, sorry), this serious topic maybe half an year later. Thanks!

Sure :-) No big deal. Just nice to have.
I wish you being just pleased by the user feedback, not being frustrated by it.
Thanks for all your great work.



Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on April 28, 2020, 21:43:38
Feedback is amazing all these years ... and most probably it's the main reason I do this day by day for more than 10 years now :).

The only problem I see > my own on my working speed ... unfortunately, it won't be better :)
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: slarti76 on April 29, 2020, 10:44:08
Something else:
May I ask about the Cloud Map/Data Storage/Sync?
Topic https://help.locusmap.eu/topic/cloud_map_and_data_storage_sync is locked, but that's 14 months ago... Is that part of LM4 or postponed because of that?
Thx for your answer!
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: joeloc on April 29, 2020, 13:14:33

@joeloc
This never worked yet. I was already thinking about it, but because no global standard exists, I left it as is now. How you may use this? Just to share tracks from your Locus to other Locus instance right?
There is quite a lot of parameters, but I'll look at it ...


Yes... share your tracks with the people you are on trips with... and also import my own tracks into Locus in a proper way. I have literally thousands of tracks from my own trips and coloring them manually in Locus is not possible any longer. I can easily generate GPXes with proper coloring and patterns in Locus syntax from a script, but that gets mostly lost on import.

In general, it just sounds reasonable if you import something you exported, it ends up being identical.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on April 30, 2020, 08:37:56
@0709
thanks a lot for the precise videos. Weird that I can't simulate exactly what happens to you. Anyway, I made some minor changes in recent code so please check the next Alpha/Beta version and let me know if the result will be the same. Thanks.

@slarti76 & others
this is really good question. I'm trying to convince Michal to write a post about our current team and what we do (or just a page "About us") but it seems it will take some time ...  :o

So shortly: even it's not visible, we grew from good old small-team (me, Petr, Michal), to six people this year (January)!
Important is that Radim firstly worked on the library for WMS maps (in preparation is support for WMTS, for voting and labels) and now he's fully focused on a new online database for POI (that will convert to offline as well).
Ondra since February work on the big web server that will first serve as a synchronization/backup server, in the second step as web route planner & data manager and later maybe also as small "community network" (not yet 100% decided). Third guy Honza (who is also the creator of the add-on for Garmin watches), work with us as some kind of "manager". I'm not a born team-leader so someone who will take care of plans & progress is definitely needed!

And that's all ... summary? I believe that we finally move with sync server and POI  & sync is a must-have for us for Locus Map 4. Because Ondra already has a month delay, it gives me time to, thanks to Your help, fine-tunes Locus Map 4 ;).

@joeloc
oki, consider as done (will be in next Alpha/Beta)
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on May 01, 2020, 08:31:19
New version 3.45.1.3 is in the Beta channel, so give it a try.

Mainly @joeloc, check if such a solution makes sense. There are parameters that have more options and there is, of course, no doc for this, so just use set > export > check method, thanks.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: joeloc on May 01, 2020, 11:20:07
New version 3.45.1.3 is in the Beta channel, so give it a try.

Mainly @joeloc, check if such a solution makes sense. There are parameters that have more options and there is, of course, no doc for this, so just use set > export > check method, thanks.
On a first quick glance, export and re-import of extra colors and patterns with gpx seem to work fine. Thanks!

Storing the Locus Database Folder there as well wouldn't be an option? Needs more thinking obviously and some UI work on the Import dialog... just an idea.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: tapio on May 01, 2020, 13:11:59
Checked Lopoints in "Nearest points" panel. Shouldn't it be independent from "Show on map" option in Lopoints window? Otherwise people will need support.
I'm glad you put some work into the POI system.

It's great that you put Locus specific track information into the gpx xml format.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: 413Michele on May 01, 2020, 14:50:50
I'm not sure if it just appeared with this version or was there before, but I noticed a problem in the strings on the Intervals tab.
I think the Climb Speed column name is made of two separate strings, I noticed because I use the app in italian and it's translated word by word. This becomes a problem when you translate to languages that don't put the adjective before the noun, because you can't change the order of the words.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: 0709 on May 01, 2020, 15:48:35
While busy now with gpx can you have a look @ the Locus result @ import to export ?
When the gpx file has an informative link in the header meta data.
@ export the metadata is removed BUT in ALL and each waypoints that link is added.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on May 02, 2020, 21:19:24
@joeloc
works ... fine.
I think that the Locus Map folder does not belong to any export format. A folder is too user-dependant, there will be need for some additional test of parent Group, maybe even folder settings ... brr, no please :).

@tapio
Well ... rather do not think too much about old "LoPoins screen", it really needs (and receive soon) some major rework.

@413Michele
hi, welcome here ;).
Well, these ARE two separate strings. "Climb" is the name for information in the first row and "Speed" for the bottom row. Check units, the climb is in "X m (up) | -X m (down)", where speed is in km/h units (or what you use).

@0709
link in top metadata ... as I see, this is made as intent. With this, probably an important link is then visible in all imported objects. The same happens for "time" that may be also in this <metadata> block. Is this wrong you think?
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: 413Michele on May 03, 2020, 10:50:00
@menion Wow, how stupid... :( I should have checked with more attention. Well, better this way!
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: poutnikl on May 06, 2020, 08:17:53
Edit: I see now I have mixed LM3 Pro and LM4 Alfa things together. As while OAM downloading is currently possible in LM3 only, the rest, related to LoPoint DB choice applies to LM4 alpha ( the DB recognition perhaps to both). But I am sure @menion will not get confused :-)
--------

I have noticed 1 not very consistent thing, related to OpenAndromaps placement during Locus-actions OAM download. It has revealed itself with existence of  new beta Locus Poi OAM dB files.

If I download OAM map or its Poi DB from OAM site via Locus actions,
it places the files into mapsVector folder. LocusMap recognizes the <country>_oam.osm.map file, but not <country>_oam.osm.db file, when I try to select the POI dB file from LoPoint selection.

If I move both files to Europe subfolder, where already are respective LoMap files for European countries, LocusMap is able to recognize the POI dB file. If I move it back to mapsVector ( all moves with LM shut down ), it is not able to find DB file again.

I am not sure, if eventual change has to be done in LocusMap application, or in the locus-actions XML file on the OAM site. But I think either Locus should place the files during the download/unpacking to the respective region folder, either it should be able to recognize the POI *.osm.db file in mapsVector as well.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: john_percy on May 06, 2020, 23:52:56
@poutnikl
Did you try clearing Locus cache? Settings > Miscellaneous > Clear temporary data > Temporary files ('cache directory'). This seems to help Locus recognise changed db file locations.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: poutnikl on May 07, 2020, 04:28:55
@johnpercy Thanks, it did help in both LM3 dB file recognition and LM4 alpha dB file choice. But it is still little strange it is ever needed.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: john_percy on May 07, 2020, 10:41:54
@poutnikl @menion
To my mind it looks as if the cache is over aggressive.

Sent from my moto g(6) plus using Tapatalk

Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on May 07, 2020, 10:49:39
I've found one minor problem when downloading OAM LoPoints so refresh of the map did not happened correctly. So try it Libor in next (Beta) version, it should work now, thanks.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: Andrew Heard on May 09, 2020, 02:04:35
I'm not sure whether to make this a new help desk suggestion, create a new general forum topic, or append to this 3.45+ topic. I leave here for convenience & thoughts from @menion...

It appears Locus ignores the Android display "screen zoom" & "font size" settings. I tried reducing both of these settings so I could see more of each point description in Nearest Points, but Locus just ignores the settings. In the screen capture below I have set Font Size=Tiny & Screen Zoom=Small to maximize the amount of onscreen text but it makes no difference. I notice that Locus refreshes the list whenever I change font size, so it is listening to these operating system events. Would it be possible/ does it make sense, to take into account the users overall preference for font size? I tried the phone in landscape mode but this didn't reveal much more of each point description. Thanks for considering.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: Andrew Heard on May 10, 2020, 12:52:17
However that help topic was a question, not a suggestion. To be fair it was answered accurately. I *really* don't want to shorten my point descriptions just so they are more readable. For context: this limitation has come to prominence with the Nearest Points feature - I can't distinguish any of the nearest points from their truncated descriptions.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on May 11, 2020, 09:43:27
@Andrew Heard
please try to fully close and re-open the app. For me, it works correctly, it just needs a restart.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: 0709 on May 11, 2020, 18:08:38
Still a problem even with the smallest Android text size set. And I do not like a change of Android standard phone setting into smaller text size just for this "manco" !

Problem:
See WMS selection window in the attached gif picture.
This is the selection text screen by the map provider !
By the way, the selection shown is:
> i Digitaal Hoogtemodel Vlaanderen II, Skyview factor 0,25 m
(Long push on item opens the info screen)

I advertised WMS use by Locus map here:
https://feedback.informatievlaanderen.be/t/raadpleegdiensten-wms-gebruiken-in-android-locus-map/180
The examples print screens by tablet display had more visible text.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: Andrew Heard on May 12, 2020, 00:22:37
@Andrew Heard
please try to fully close and re-open the app. For me, it works correctly, it just needs a restart.
@menion - a restart makes no difference - the descriptions in the Nearest Points list are always the same font size. Since my last post I have some more observations:
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on May 12, 2020, 11:01:09
@0709
thanks Willy. I know well about the problem in WMS screen. It is probably the worst case of this because many WMS maps have really long names for layers that often start with the same text (btw. nice post about WMS usage).

So at least one change
- changed font to "Condensed" variant

@Andrew Heard
nice screenshot = nice example of how big difference is between fresh new design and maybe 5 - 6 years old design of point/track screens. Have to change it ...

Anyway, let's try to improve it. So two changes and we will see what your device says :).
- changed font to "Condensed" variant
- enabled option to break the first line to two rows
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: Andrew Heard on May 12, 2020, 11:47:30
@Andrew Heard
For me, it works correctly, it just needs a restart.
@menion - are you saying the Description text in your points/ tracks/ nearest points lists are affected/ altered by the Android system-level displayed font size setting?

So two changes and we will see what your device says
See on your device too? Aren't you seeing the same issue with a longer-than-15-character point description in Nearest Points list?

- enabled option to break the first line to two rows
Do you mean a user option, or just not worded how you meant? It should be automatic like the track & points lists, not an option.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on May 12, 2020, 14:09:32
On my device, I see 26 characters, so I never considered this a big problem (old Pixel 2 device with average resolution).

Check this video (https://drive.google.com/file/d/1N0kPf6UHI7qA5lvzM982LrP6sK84kIWN/view?usp=sharing). Your device has from time to time some weird behavior :).

And sorry for my English, I wanted to say enabled break of the first line to two rows
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: Andrew Heard on May 13, 2020, 00:32:14
On my device, I see 26 characters, so I never considered this a big problem (old Pixel 2 device with average resolution).
ahh stupid Andrew - each time I tested the change of Android settings > Display > Font & Screen Zoom, I forgot to tap Done at exit, so the settings were simply ignored. I now confirm the text height is indeed changed to reflect this setting like your video. I do agree with @0709 it should not be necessary to change this global setting for the need of one app, Locus. I think the final result of harmonizing the font, and line wrapping for consistency with the point & track lists is still a good move forward.

Your device has from time to time some weird behavior :).
just weird owner

And sorry for my English, I wanted to say enabled break of the first line to two rows
infinitely better than my Czech ;) & as @menion always remind us, no need for sorry
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: Žajdlík Josef on May 14, 2020, 06:10:45
In the new Beta version, the context menu does not work after a long press of the button.  For example, the ability to turn off GPS.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: Žajdlík Josef on May 14, 2020, 08:17:13
3.45.1.6 long push button > menu > ok

long press of the button
- menu button (after unpacking with a hamburger) - OK
- toolbar button - not working
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: Žajdlík Josef on May 14, 2020, 11:26:27
After reinstalling on BETA LM4 MapGooglePlay_3.45.1.6 LM4_933_beta.apk long press of the buttons works.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: FriedelXT on May 14, 2020, 20:53:50
I miss the new "round" design
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: Christian on May 15, 2020, 17:00:48
When using the button "Exit" in the right bar Locus is terminated without confirmation which is activated in expert settings (confirm on exit = enabled).
:(
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: Christian on May 16, 2020, 12:02:41
Additional question: Is this a Android thing that the Android bottom bar disappears or is it triggered by Locus? The hidden bottom bar is the reason i have to use the Exit button. See above.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: tapio on May 18, 2020, 16:48:38
Additional question: Is this a Android thing that the Android bottom bar disappears or is it triggered by Locus? The hidden bottom bar is the reason i have to use the Exit button. See above.
Isn't that related to fullscreen mode of Locus?
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: karlchick on May 18, 2020, 18:22:52
Just spotted this new development of linking PDF legends. I'm guessing that we can only have one legend PDF per theme (per locale). My OS Map theme contains two styles of maps, so has two legends. Attached is a PDF that combines both legends into a single PDF with a front page index with hyperlink to quickly jump the relevant legend section (Explorer 1:25k or Landranger 1:50k).

The map legend index list on front page are each clickable hyperlinks/shortcuts to relevant legends. But not all PDF viewers support links in PDFs... Acrobat does on Android works fine though...

Karl.

Update: I've joined the beta release scheme, downloading latest...  Yay! It works!

Not so keen on the overlayed green icon indicator blocking the theme logo, I could change the os map thene logo to better suit the indicator... maybe
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: Christian on May 19, 2020, 21:54:43
Additional question: Is this a Android thing that the Android bottom bar disappears or is it triggered by Locus? The hidden bottom bar is the reason i have to use the Exit button. See above.
Isn't that related to fullscreen mode of Locus?
Yes, thanx. I had fullscreen mode activated since years but the Android bottom bar disappeard since a couple of weeks.
Shall I expect that the Android bottom bar should re-appear when double tap on the screen and the LM bars appear  - means, the fullscreen mode is deactivated?
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: poutnikl on May 19, 2020, 23:05:47


Yes, thanx. I had fullscreen mode activated since years but the Android bottom bar disappeard since a couple of weeks.
Shall I expect that the Android bottom bar should re-appear when double tap on the screen and the LM bars appear  - means, the fullscreen mode is deactivated?

Just by chance,
can it be the case you have  activated Android swipe gestures instead of prior soft buttons Back/Home/Tasklist ?
( Settings, System, Gestures System navigation )

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: Christian on May 20, 2020, 17:25:40
No. The soft buttons are activated.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on May 21, 2020, 12:50:54
@Christian
generally full-screen support in LM is not perfect. It needs to be updated to match current possibilities. I personally did not make any changes in current app system, but as a side-effect of updates of some Google libraries, it is possible that something changed. I've at least for now fixed behavior of the "Exit" function.

@karlchick
very nice!
Currently yes, only a single legend per map theme is possible. It seems you solved it perfectly :).
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: Christian on May 21, 2020, 17:05:38
Thank you. I can live with that.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: slarti76 on May 23, 2020, 10:15:39
Weird "Process successful" toast
Yesterday, I went biking, but had Locus recording the track, but mostly running in the background (yes, I was sometimes playing Pokémon Go...). Which was running fine, but every few minutes, there was a green "Process successful" toast popping up. I'm pretty sure it's a Locus toast, had the exact look and text that I know from open Locus. But there was no user interaction for which a toast was warranted. Everything was running fine.
I have no idea what could have caused that (saving track part perhaps?).
If I'm right and it was Locus, I think Locus shouldn't do toasts while in background, especially not if everything's fine. Another thing would be an error, but at least there should be more information what actually happened...
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: slarti76 on May 23, 2020, 13:51:53
Another thing:
See the attached screenshot. An obviously unrealistic hiking time estimation: The profile says "600 Vm/h" downwards, but the whole track with 640m descent and even 80m ascent should be done in less than half an hour?! I know these calculations are rough at best, but that is sooo off...
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: poutnikl on May 23, 2020, 16:39:44
I tried to calculate a mountain hike I once took from Cortina d'Ampezzo to Tofana di Rozes in Dolomites I once took.

The way up was about 13 km and cca 2000 m ascend. I have selected  Take a hike profile in LM4 beta b936 which  calculated about 10.5 hours.

But it calculated about the same time for the trip up and down 26 km long. ( using the mountain top as viapoint ).



Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on May 25, 2020, 06:53:51
@slarti76
I'm sure, you will recognize app toast as no other app I know have such colored popups. Anyway simple "Process successful" is called a hundred times in the app, so it is impossible to say what it means. Maybe some ANT/BT sensors that notify on correct re-connection?

Incorrect time in the "Trip time" screen happens also with the latest beta? Because I made some changes there.

Anyway same for @poutnikl : in case of weird values, please share a GPX with me so I may simulate it. Or if anyone interested, I may gladly publish the source code of this pretty simple algorithm. Maybe someone will be a better idea of how to do it.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: poutnikl on May 25, 2020, 07:23:05
I have attached export.zip, containing 2 TofdRoses GPX files.

1 is just way up from Cortina d' Ampezzo to Tofana Di Rozes, generated by BRouter, 2 is with additional way back down. It is about 13, resp. 26 km, cca 2000 M ascend. ( The route is just for the debugging, the true path up was then along the west side ferrata )

Both are provided in the Route planner with trip estimation time cca 10h 38 min with profile "Take a hike" in LM4 beta 936.

But what I have not noticed earlier, the track manager shows for these routes some crazy values, like 430000 resp.870000 hours. It seems like an ugly bug somewhere.


http://cloud.tapatalk.com/s/5ecb53367b6c6/export.zip (http://cloud.tapatalk.com/s/5ecb53367b6c6/export.zip)

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on May 25, 2020, 08:10:10
The stupid issue, thanks a lot Libor!
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: slarti76 on May 25, 2020, 09:19:00
@slarti76
I'm sure, you will recognize app toast as no other app I know have such colored popups. Anyway simple "Process successful" is called a hundred times in the app, so it is impossible to say what it means. Maybe some ANT/BT sensors that notify on correct re-connection?
Nope, nothing special (or not-so-special) connected.
And my question was more if Locus should really show such generic toasts when in background at all. Error messages, sure, but a simple "everything's OK" when in background? My email app also doesn't show a toast when it checked the server without an error (and without messages).
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on May 25, 2020, 09:21:53
Locus also does not show such toasts when for example check for news or any other background task. This have to be a result of some more important operation, that's why there is such a "useless" toast. If this will continue in the next versions and you'll want to solve it, I may prepare a version that will print out into a log, which function displayed this info ...
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: slarti76 on May 25, 2020, 10:11:08
Locus also does not show such toasts when for example check for news or any other background task. This have to be a result of some more important operation, that's why there is such a "useless" toast. If this will continue in the next versions and you'll want to solve it, I may prepare a version that will print out into a log, which function displayed this info ...
Wouldn't it make sense to put more information in this toast in any case? Like, eg. "Locus: BT reconnect successful"? I mean, perhaps it turns out it's a useful toast - I didn't want to imply that it's useless in any case. I just think something as generic as "Process successful" should only ever be used as a direct result of a user interaction.
Title: Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
Post by: menion on May 25, 2020, 11:29:41
Till now, I never considered this as a problem. Such a message almost always popup as a result of any visible action. So usually you directly see for example "Exporting..." dialog and then popup this message.

So sure, it makes sense to have more info in this your popup, it is just usually not needed.