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 ... 724
Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 13, 2019, 20:21:56 »
This is correct. With V4 maps, app has no idea which map is used, so always first selected (primary) map is displayed in the top bar and also in map manager.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 13, 2019, 16:08:35 »
New version 3.38.4
- mainly fixed major problems

correct, I still believe current behavior works correctly. As I wrote, there is a need for one tiny change that causes a little trouble for me. If you set 150% to magnify, the app just needs to do zoom by this 50 % (like by fingers) and then all will work as expected. Anyway, let it be for now, I'll invest more time to it and in next Beta ...

Problem with white areas reported by you and Josef are still not reproducible by me and colleagues, weird. Will need to play with it a little more.

perfect you found reason. It means I should be able to simulate it. Weird is that Locus do not search in HGT files and mainly in zoom level on your video, shading should be completely disabled! (it should work till level 8+)

Troubles & Questions / Re: Phone Compatibility with 3.38+
« on: June 12, 2019, 13:54:14 »
Good day Doug,
I'm sorry, but this issue has to be on Google Side, not on ours. I only see in Google Play console where we upload new app versions, that your device is supported and that there are currently 315 users who use Locus Map. Latest version? This is not unfortunately visible.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 12, 2019, 13:43:54 »
unfortunately together with my colleagues, we are still unable to simulate this problem. No matter what we do, it simply works. Are you using any overlay or WMS map?

all other vector maps, except LoMaps, has defined area as big bounding rectangle. So huge maps like these you use, may have areas completely without a map, but Locus is unable to detect it because the definition in the map tell that this empty space should be covered. So I may currently highly recommend using more smaller maps then two huge.

I'm still quite sure it works, it only does not immediately change what you expected (visible camera scale). Try to use hardware zoom in/out after you change magnify and you will for sure see difference.
Anyway blank screen with combination with zoom lock is weird. Can't simulate, but will be watching it.

Hi guys,
hmm, I'm unable to simulate it. LoMaps + internal theme ... simply search for an address and when map moves with animation to found place, this (your screenshot) is the result, right?
Any map set as overlay?

Good day Nick,
interesting. This issue is in Locus Map for maybe two years and finally, with 3.38, I was sure that issue is finally solved. Seems not, hmm.
A quick hack is to press the back button more than once quickly.

Anyway, I just made a better useful solution: like in some other screens, I've added small floating "home" button to bottom left corner which returns directly on the main map screen. So next version. Thanks for the bug report.

Maps / Re: Need help converting overlay for use with Locus
« on: June 09, 2019, 08:57:54 »
just my quick check ... there seems to be available KML format. It should be fully supported by Locus Map app (as well as Locus GIS). Did you try to import this format?

Maps / Re: IDs of custom online maps
« on: June 09, 2019, 08:55:48 »
the only limit is really just ID value. It has to be above the mentioned 1000. And yes, it has to be a numerical value as well.
In case of multiple custom ID ... first win and (maybe) Locus will warn about duplicate ID's.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 07, 2019, 14:14:40 »
New Beta just uploaded on Google Play

I understand your precise description, unfortunately, I wasn't able to simulate this issue. Give please a try new Beta as well, because I made some improvements that may affect this as well.

@John Campbell
new account? It should be possible to change almost everything in the old one like email address etc. Anyway coastlines are not directly available in the app.

ah damn, thanks. Second try ...

@Andrew Heard
wakelock is expected in case of enabled GPS. Locus Map keeps wakelock active as long as GPS is needed.

Troubles & Questions / Re: Phone Compatibility with 3.38+
« on: June 05, 2019, 09:05:32 »
It won't be this case, 3.38.3 is already published to 100% of users.

As I see in our Google Play console, there should be no problem with your device. Sorry, but this problem is out of our possibilities, no idea how to solve this. Give a try to the simple restart of the device or clearing a cache of Google Play app.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 04, 2019, 22:30:32 »
can't say that I agree with "when you reach the sea you are at 0 mt no more shadow needed", but let's say here should not be a shadow. Anyway as sonny wrote, give us some data. Based on your scale and precision of HGT files supplied over Locus Map (around 50 m if I remember correctly), it will be most probably result of interpolation.

Petr was able to simulate something, thanks for pointing on this problem.

@Andrew Heard, @tramp20
oki, thanks for the info. Really hard to solve somehow, without more precise knowledge where may be a problem. Hmm will have to do some tests ...

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 04, 2019, 08:45:24 »
Ah yes ... I did not touch track recording directly, but functionality before (work with received GPS location) is affected. So yes, location filter is applied directly on received location and then all functionality in the app use this modified location. Anyway, it is just a few matrix operations once per second, so it definitely cannot increase power consumption by 1%.
You may anyway give it a try Andrew by disabling location filter in settings > GPS & Sensors > Location filter.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 04, 2019, 08:19:14 »
what exactly is wrong with shadows? HGT files used for rendering of shadows may not be the same as used for creating map and it's elevation lines.

automatic map change: be more specific please. Which map, how they are stored on your SD card, what settings you use, thanks.

@Andrew Heard
interesting observation. As @tommi correctly mentioned, if screen is off, there is no visible map = no matter what I changed, it should have no effect here. If only running is track recording (is it?) then it is surprising, because I did not touched anything regards track recording service for a long time. Please keep tracking and confirm this, thanks.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 03, 2019, 20:03:46 »
Ah yes, new Beta is out.

And it is ... hidden behind "many smaller fixes". I've spent some time searching for possible performance problems. Some changes may be visible for you, some not. But if your personal overall feeling is "faster" = perfect.

"united" (reaction on the last post)

Pages: [1] 2 3 ... 724