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 ... 726
Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: Yesterday at 19:52:06 »
Thanks, I noticed this issue today as well. Groundspeak seems to make some changes in API that break Locus Map implementation of this geocaching feature. I've already fixed it. The new version will be published most probably on Thursday.

About map slowdown ... it is complicated to solve it with current Locus Map version. I'll need a small help from you, but little later when I'll publish the new Beta version. I'll then write (Beta? during next week for sure) more if you will be interested to invest little time into test.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: Yesterday at 13:30:11 »

Autoloading for vector maps works for maps that match the following conditions:
  - same map version (so V3 + V4 do not work at once)
  - same tilesize (LoMaps compare to other maps usually have 512x512px per tile)

Anyway thanks for additional information. It really has to be highly dependent on maps we have in Locus Map available, because no matter what I do, I see only single valid coordinates from the current base map. John, even if I'll be able to simulate it, I really have absolutely no idea how to fix it ...

Some answers are above in answer to John, rest then:
- internal themes works only for V3 maps.
- auto-loading maps may be a big problem for huge maps that cover a big area. Maps are defined only by its bounding rectangle and Locus Map is unable to correctly detect missing area and coverage of other maps. Sorry, I do no have improvements in the head here.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: Yesterday at 08:34:01 »
You wrote " it happens when I use a WMS raster map, a V4 overlay map and turn on map rotation".
This I understand as base map layer + map overlay (V4) +  WMS map = 3 maps.

S8 is more powerful than my device (Pixel 2) and I see no serious problem with rotation of these three layers so there have to be something different.

Do you have enabled "Hardware acceleration" in Expert settings? (maybe you do not know Expert settings, then it's OK, this option is enabled by default). Otherwise map is empty, no huge number of points and tracks somewhere on the map?

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: Yesterday at 00:06:55 »
may you please give me coordinates where is the problem with the double-elevation lines most significant? Because I downloaded two mentioned maps from OpenAndroMaps and I'm unable to see this problem. Thanks

hmm there should be no problem with BRouter on Android 5.x, weird.
Shorted log: best what you may do is to create basic log by the known method, remember a time when the problem happens and from generated TXT file just extract part around this time. Thanks.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 24, 2019, 20:50:14 »
I do not know the device you have, but three map layers at once together with map rotation ... well, I do not expect an amazing performance here.

so should I understand that once app start recalculates, it displays only some errors and no result is computed? What router are you using and what is your Android version? Also are you able to create a bug-report log by this method right after these issues happens?
Ah in the second post you mentioned BRouter. Did you tried the same route with GraphHopper routing?
S5 Neo is not the best device, on the second side, shorter routes should not be a serious problem.

long click on the map, click on the popup to display point detail, click on bottom navigation > Guide on and result? App returns to map with enabled guidance to point and popup is hidden. Since we talked about it, I definitelly did not touch this part of code. And in your case, popup is still visible, right?

[CZ&SK] - diskuze o Locusu / Re: Úsporný profil záznamu trasy
« on: June 24, 2019, 20:35:31 »
profil jako takový nikoliv. Když už tak spíše jeho vedlejší efekt: tedy čím více bodů (hustší záznam), tím více výpočetního výkonu spotřebovaného na filtrování, ukládání, vykreslování na mapě. Takže doporučení: 1 bod za 20 metru bude určitě výrazně efektivnější než dob každou vteřinu.

Obecně největší "žrout" energine je displej a pak hned GPS. Takže méně se dívat na displej, to je základ.
Pokud by jsi chtěl extrémně šetřit baterii, lze využít funkci "GPS auto-off", která udělá opravdu hodně ale rozhodně doporučuju se s tím nejdříve více seznámit a vyzkoušet protože při nesprávném použití můžou být záznamy k ničemu.

Možná ještě někdo další bude mít praktické tipy ale za mě hlavně takto.

[CZ&SK] - diskuze o Locusu / Re: ZOOM level ve verzi 3.38
« on: June 24, 2019, 15:18:05 »
No jo, jsou tam i vektorovky, to mi prošlo omylem, díky, opravím :).

Jinak když si otevřeš správce map, tak pokud je mapa stažená Locusem, má dole ve druhé řádce pod jménem ještě poskytovatele. Takže ten stejný typ je řízen tímto poskytovatelem. Nicméně už jsem na tohle nastavení koukal a moc dobře nefunguje, takže určitě v některé z dalších verzí odeberu a bude z toho spíše "načítat ano/ne" s tím že mapy od stejného poskytovatele budou mít nějakou preferenci.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 22, 2019, 17:37:09 »
@poutnikl , @john_percy
I've found that "zoom lock" seems to be completely broken now, not just the scale bar. Fixed ...

is there any information about why it should be so big problem? I use this system for many years and I believe many users as well and I'm not aware of any problem. Or this is only about "moon reader dev told me"?

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 22, 2019, 11:51:56 »
oki, so zoom lock :). ... ah, I see ... bottom "map scale" bar isn't refreshed now, thanks! After zoom in/out it refreshes correctly. Consider as fixed.

@Henk van der Spek
automatic loading between various map types is no possible and planned.

thanks for the steps, I'll look at it.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 22, 2019, 11:24:35 »
isn't it same like when you pick real magnifier? It also displays the same object but enlarged. And not some modified scaled clone. Are we talking about magnifying glass on the screenshot below? If so, which scale is incorrect?

hmm I'm checking it and "Fill map gaps" should not be affect by any feature. There is need to see difference between effect of "smooth interface" and "fill map gaps".
"Smoot interface" is able to reuse map tiles from current visible zoom level during zoom to other zoom level. Nothing more. When you then scroll by map to are without a map in current zoom level, it has no effect.
On other side, "fill map gaps" should be able to search in available zoom levels of the current map and fill empty spaces on the screen by map tiles from different zoom levels.

Map overview for the track: complicated unsolvable problem. With LoMaps, this most probably does not happen because they have exactly defined coverage area. So question here is how to get more precise coverage for other vector maps as well ... hmm.

I still did not noticed this issue, never. I'll add it to my todo list, but to be true, I currently have absolutely no idea how to solve it ...

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 22, 2019, 09:00:08 »
 ... really funny is that: how it works in recent version is exactly the same as it worked in previous (at least from the developer point of view) except one tiny detail ... the map immediately displays (zoom in/out) result of "magnify" change.
Well ... fine, one part of bigger problems solved, uff :)

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 22, 2019, 08:31:35 »
then there have to be something, that slow it down. A huge number of points, tracks visible at once?
I'm aware of this issue, sorry for this. Needs more work and testing, so till next 3.39, I'll for sure look at it.

current values are chosen to have as close as possible style of raster and vector maps. So in most cases, texts should be the same size for same zoom levels etc. Of course, it highly depends on the map (mainly raster) theme. So I would like to keep it simple.

Map themes ... as I wrote, Locus Map checks for xml files in one subdirectory level. You placed xml files into second subdirectory level (relative to "_themes" directory), so Locus Map is unable to find it.

nastavení bude přidáno do expertního nastavení přímo v apce v další 3.39+ verzi.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 21, 2019, 16:57:50 »
So good news, nice.

I see in crashlytics (system for automatic collecting crashes) few crashes when using vector maps as overlays right after the start of the app. Hope it's just a few rare users ... otherwise, app looks pretty stable.

I also did last days few performance optimizations so hope, it will be fluent and usable like at early days :). Enjoy weekend!

Hello franc,
one year without response, sorry for this.
Is this issue still bother you or it does not happen anymore on your device?

Pages: [1] 2 3 ... 726