Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - menion

Pages: [1] 2 3 ... 16
2
Well as I see, icons are at least 5 years old so agree, very nice for modern devices :).

On the second side, it is almost 300 icons and web https://mapicons.mapsmarker.com/ does not offer higher resolution ... but a good point of course.
The following users thanked this post: luce

3
Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: May 28, 2019, 17:51:01 »
As John already mentioned, hopefully, final new version 3.38.3 is out.

As I wrote on help desk (copy content here):
If you still won't be satisfied with how maps look like or behave in latest 3.38.3 version, here are a few tips:
  • automatic scaling: may be disabled in Settings > Maps > Advanced features > Optimized raster map resolution
  • slower zooming: check automatic loading in Settings > Maps > Offline maps or alternatively you may try to disable some map animations in Settings > expert settings > Smooth interface
  • incorrect display of 512x512px online maps: 512x512px tiles with same indexes (x, y) as for 256x256px does not make sense. Previously it worked more like an accident then an intent. Do make it work correctly, it is needed to use the method I described here.

Thanks for your help here and also big thanks to a few quick translators!
The following users thanked this post: erfi

4
If you are still using MotoG device, the difference in your case should be 2x rescaled tiles when this option is enabled (so 1x1px of the map should be drawn on 2x2px on the device screen).
The following users thanked this post: George Oscar

5
Good point ... hmm quick fix placed into an incorrect section.
Anyway, it will work ...
The following users thanked this post: George Oscar

6
Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: May 23, 2019, 17:16:54 »
@tramp20
1. have no idea. Does this happen everytime you start the app or just after the update?
2. interesting problem. No support for Tasker or similar app exists currently.
What I suggest: set automatic backup to once a day and let it be. The app may really start backup in defined time +- few hours! App also needs a valid wi-fi connection. I plan to change the logic behind to one more reliable system, but it will need some time.

@CabrioTourer
Free version does not support "Folders". They are anyway stored in the database, so data are not lost.

@tramp20
what you mean by "favorites"?
The following users thanked this post: CabrioTourer

7
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 22, 2019, 13:22:47 »
These were quite long two months. It is probably for the first time, I publish a version after such a long time since the previous release. Last two days I spend by fixing various problems we found and just now, the new version was published on Google Play.

We have an option to publish version only for certain part of users (probably random selection). So today, it will be only for 10% of users. If there won't be any unsolvable problem, I'll enable version for all users tomorrow. Thanks for understaning.

And mainly thanks for the help. Update of map system was a big task for me and I'm really glad, version with this change is out. Now we can fine-tune it :).
The following users thanked this post: Andrew Heard, CabrioTourer

8
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 20, 2019, 12:43:35 »
Got it, perfect, thanks.

Btw, for video, most of us here usually use the very nice tool: https://play.google.com/store/apps/details?id=com.hecorat.screenrecorder.free . Might find useful ...
The following users thanked this post: Žajdlík Josef

9
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 20, 2019, 08:11:03 »
@erfi
thanks, you are correct. "Walking" was dependent on speed, but "Hiking" no. It was hardcoded to a single value per km. I've improved it and based on information I've found, changes are: "hiking" will use same values for computing of energy consumption like "walking" + 15%, which should be equal to carry 5kg backpack.

@Žajdlík Josef
hmm. Even with Czech description, I do not exactly understand where is the problem. Should be possible to create a short video of this problem? Thank you!
The following users thanked this post: erfi

10
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 13, 2019, 17:20:57 »
Uff so seems good news, thanks guys.

What I have found and fixed since 3.37.2.13
  • sometimes not reliable "hold map center"
  • still visible LoPoints after switching from LoMap to different map (needs a better approach in future)
  • not working LoPoints attached to any other vector map (V4 OAM for example). Now it works as well.
The following users thanked this post: michaelbechtold

11
Troubles & Questions / Re: Problems with navigating a route
« on: May 13, 2019, 12:53:47 »
@0709
Heh, same as in my answer 11 days ago on the help desk, I mix two cases, sorry :).

We talk here about recalculation, so I again wanted to say that for point-priority, via-points are must-pass.

Anyway, new version 3.37.2.13 just published and it should solve
a) issue with via points & route-priority as in attach file (thanks for help)
b) added hopefully nice tool that should prevent recalculation back if user ignore "turn back" 2 times. So if you ride forward, app two times recalculate back and you still ride forward, 3rd recompute should be forward and not backward.
The following users thanked this post: Andrew Heard

12
Hi,
package!
"menion.android.locus" > Locus Map Free
"menion.android.locus.pro" > Locus Map Pro
The following users thanked this post: freischneider

13
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 12, 2019, 17:35:47 »
Yes, I'm seriously thinking about it and I already have a solution in the head.
The following users thanked this post: CabrioTourer

14
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 12, 2019, 15:56:35 »
Hmm, this one will be complicated, sorry for this.
It's some weird problem in Kotlin language and I have no idea why it appears now and how to solve it. I'm playing with it since morning and I'm unable to simulate it on own devices > so I'm unable to verify if some changes fixed it. Anyway, I updated a few core libraries that create required apk file, so we will have to give it another try with version over Google Play. Thanks for understanding and patience.

@michaelbechtold
I may check the scaling of overlay once more, but I think it works correctly now. App no longer works with "zoom values" as are stored in SQLite database. In map core is so called "zoom scale" parameter and app try to find best available tile zoom to display. Hmm, I'll maybe try to write some blog post with explanation of this system.

@Žajdlík Josef
reset of auto-zoom was mentioned in app news.
I've made now conversion of old values, but still highly suggest to check results, because conversion won't give 100% correct values. Old stored zoom value can't be 1:1 converted to the new value.

@tramp20
funny. I made no change in the auto-backup system ;)

@zossebart
Android 4.x was my pain for maybe 2-3 years. With Android 5.x I have no single problem, all works as I need. So I can't imagine a single reason why to drop support for these Androids. Something will come, but definitely not in the nearest years.
The following users thanked this post: Žajdlík Josef

15
Every app has its a visible name like "3.37.2" but also need a special "version code" number.
In the case of Locus Map, I increment it by 1 with every public update (also Beta versions). So now it is public version 827 since I started to work on Locus app :).
The following users thanked this post: Andrew Heard

Pages: [1] 2 3 ... 16