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] 4 5 ... 720
Troubles & Questions / Re: Route planner - crash when resuming
« on: May 08, 2019, 09:47:15 »
Quite interesting.
We play to publish new Locus Map version in the middle of May, so if possible, give it a try (you may simply try a Free version as it shares same code) and let me know, thanks.

[CZ&SK] - diskuze o Locusu / Re: Větší písmo
« on: May 08, 2019, 09:46:01 »
tohle bohužel aktuálně nejde.
Celá ta navigační obrazovka doufám že již letos dozná zásadnější změny a lépe viditelné informace jsou jednou z těch hlavních.

Dočasné řešení je možná nadefinovat si vlastní Dashboard který zobrazí co je potřeba dle vašeho uvážení (pozice, velikost atd). Pak tam sice bude viset ten horní panel s malými údaji ale jak jsem psal ... věřím že to je dočasné řešení. Díky

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 08, 2019, 09:41:43 »
weird, all work for me on Android 9. What happens when you "cancel" backups and then set them up from scratch?

@Viajero Perdido
hmm, specific use-case. Anyway, I'll check it, but correct should be to close whole big screen with available PQ files right after import starts.

ah, ugly issue. Thanks, offline search fixed.

This problem with contacts is in the app for many many years. Press "back" twice and it will be ok :).

well, not sure what is the problem. Fact that you can't recalculate the whole route with other then BRouter engines? This is not an issue as notification say.

Troubles & Questions / Re: Problems with navigating a route
« on: May 05, 2019, 15:18:12 »
Hello Willy,
what is the difference between the first two videos? I watched them more than once but still does not see any significant difference. Thanks

I'm just tested Strict mode and it seems to work the same as before.

Troubles & Questions / Re: uploaded POI icons disappeared
« on: May 05, 2019, 10:32:07 »
Hello Alan,
if I understand correctly, a similar problem happens in the case, you use some "clear cache" or "optimize device" method (or something very similar) in Samsung devices. They optimized device so much, that this deleted all custom icons placed in Locus/icons directory. Maybe this is your case?

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 05, 2019, 10:04:12 »
@tommi, @erfi
ah, thanks for the route planner issue with the center of the screen. The same issue happens also on other secondary screens with the visible map: fixed and also fixed correct map scale, thanks.

I'll have to look on this topic more this week, thanks.

@Viajero Perdido
I think I've got it. The issue with the loading of PQ fixed.
Importing of PQ files should finish on the map I think. App should load a PQ from the internet and start an import. If you want to import more PQ at once, isn't better to directly select all of them in the list?

I wrote to Arcao a few days ago, but still no response. He is not active on Facebook, no changes on his GitHub account. No idea what happens.

And still working ... it should stop work on 1. 6. 2019. Groundspeak increased their dead-line till the end of May.

[CZ&SK] - diskuze o Locusu / Re: Vrstvy map
« on: May 04, 2019, 20:00:57 »
tohle bohužel zatím v Locusu nejde. Opravdu mohou být vidět pouze dvě vrstvy najednou, více nikoliv. Takováhle funkcionalita je již možná v Locus GIS aplikaci, ale ta se zase moc nehodí na turistiku, cyklistiku.

Dříve byl důvodem omezený výkon na straně zařízení. teď už je to spíše protože nikdo více o takovou fci neloboval a ani na tom nebyl čas a ani aktuálně moc není. Díky za pochopení.

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 04, 2019, 13:19:38 »
I'll discuss this with Petr this week. Not sure if a little decrease in shading is necessary because of one bad combination of yellow & yellow that is not so usual.

And forum, well, next time smaller attachments. Hard to help :).
recalculation should work also when the screen is off (except known problem to me with BRouter on Android 8). Weird. 30 second is there as a simple prevention of too frequent computations. Distance is definitely not enough to limit it. Distance even a 200m in car is really short and recalculation every few seconds, hmm not sure if ideal.

right after start, thanks, I'll test it.

tilting was again removed. It was enabled by accident, sorry.

And nearest points: good point. I've added this to list of "LoPoints improvements".

Troubles & Questions / Re: Problems with navigating a route
« on: May 04, 2019, 13:08:20 »
Hmm not best. Recalculation with route-priority, "stick to route" disabled, right?

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 04, 2019, 08:11:40 »
hmm, yellow road on yellow background :/

Forum isn't ideal in more ways, agree. I think a lot longer time to move it to a different system. Discourse looks nice, but we use it on our help desk for Locus GIS and can't say I'm 100% convinced it is the best system.

@Andrew Heard
yep, I had to remove this option for now, because it does not work as needed. Will have to find more time and create a new system for this setting.


Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 03, 2019, 23:07:15 »
Well, for the planned route it may be a few kilometers. Anyway, for the manually recorded track used later for navigation, this may reduce to a quite short distance, so agree it is not an ideal solution.

As I think about it, testing on nearest trackpoint may not be so big problem. Because automatic recalculation is trigger max. once per 30 seconds, app should search over whole track without any limit.

On the second side, this quite nicely solves a possible issue with round routes.

EDIT: as Pountik wrote.

Generally, using any exact limit is usually not the best solution. So why 100 trackpoints? Usually it will work, sometimes not, like on your case.
On second side, what if you ride in the middle (on your video it's a first char "a" in name "Leiblachtal"), app snap to the bottom line, but it was only some detour and then you return back close to start of this route?
Just want to show that any change may on cause malfunction of different use-case. So I still see here as backup solution easily accessible button "nearest point".

myslím že neřešilo.

Tady moc možností modifikace zatím není. Jen jak bude trošku více času, rád bych začal pracovat na upravení téhle komponenty a nabídl obecně lepší možnosti zjišťování informací o trase na mapě a i práci s ní. Žádný rychlý tip tedy nemám, nabízím vyhlídky na lepší zítřky :). Díky za pochopení.

Discussion/New features / Re: Update of map core (2019)
« on: May 03, 2019, 19:14:02 »
I'm 100% sure that DPI applied to raster maps is the correct method. Why? Texts, icons, whole UI, almost everything scale based on device DPI because there are huge differences between small and huge resolutions. And only raster maps are still ... same.

New Beta version is already available on Google Play so feel free to test it. I believe that 0.5 value will be an ideal compromise for smaller and also bigger devices.

Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 03, 2019, 19:10:31 »
slower simulation is possible, not all "activities" have defined average speed. Best is to use base activities like walk, run, bike, car.

Thanks for the very precise bug report. The problem here: you took a really huge shortcut here. To improve performance, app tests only following 100 trackpoints, so seems that whole missed part is more than 100 trackpoints. As a save-button, in navigation menu is "nearest point" button. Anyway this is interesting and probably common use case. I'll think about it, thanks.

Frequency of recalculation: there is a limit to once per 30 seconds. Was there always. Anyway seems, based on confirmation, there is any new problem. I'll check it.

Map core has priority, but without navigation working at least same as in 3.37.2, I cannot publish new version, so thank you for testing!

it is correct. I spend on this today maybe two hours and it really isn't so easy task. Currently not solved without a clear idea how to easily solve. It just needs some sleep and good tea :).

Pages: 1 2 [3] 4 5 ... 720