[APP] - version 3.41.+ ( 7. 11. 2019 )

[tapio]

The new App picking in Favourites has some "low fps" vibe, very stuttering, what is this related to? It is existing at a few places in Locus. Also, if I add a waypoint to a track and ckoose "Select on map", the map performs low.

[Menion]

By "low fps" you mean a slow scrolling or the fact that it takes some time till the screen with app selection appears? The same screen is available also when you edit function panel, so expect that you have the same issue there as well.
Slow map ... hard to say what it may cause? The map on the main screen works well? Usually, a restart of the device solve most of problems .

[john_percy]

@menion
https://www.google.com/maps/search/?api=1&query={mapLat},{mapLon}&zoom={mapZoom}

http://www.google.com/maps/@{mapLat},{mapLon},{mapZoom}z

geo:{mapLat},{mapLon}?z={mapZoom}

https://www.google.com/maps/@?api=1&map_action=map&center={mapLat},{mapLon}&zoom={mapZoom}

I'm not sure if the search function (first link) supports zoom

(The displayed link is truncated but the actual link can be copied from a quoted reply. Setting it as "code" doesn't work perfectly either in Tapatalk.)



Sent from my moto g(6) plus using Tapatalk

[Menion]

Hi John,
easy to test out of LM.

1. ... no effect
https://www.google.com/maps/search/?api=1&query=50,14&zoom=12
https://www.google.com/maps/search/?api=1&query=50,14&zoom=18

2 ... should work
http://www.google.com/maps/@50,14,12z
http://www.google.com/maps/@50,14,18z

3. ... should work
https://www.google.com/maps/@?api=1&map_action=map&center=50,14&zoom=12
https://www.google.com/maps/@?api=1&map_action=map&center=50,14&zoom=18

---

Test in Locus Map was positive (I just tried 3rd option) and it seems to work correctly at least with Google Chrome and also with Google Maps app (there seems to be some kind of zoom animation, so not sure if displayed zoom was exact).

[john_percy]

@menion
Thanks for the testing. I now see that the www bookmarks return different zooms with Google. However, they do not correspond with Locus zoom levels, which is probably the reason I missed it before. I appreciate that this may be difficult to implement partly because of the difference  of zoom numbers between Lomaps/MF3 and MF4 maps for the same map area display but it would be really nice if you could build in some correspondence so that the mapZoom tags have the equivalent value that Google would use.
Would you like some screenshots to illustrate this or have I explained?

[Menion]

Not sure how may I help here. If you display in the top toolbar "Map" label, then you should see the value that is set in the defined URL template. Maybe in case, you use some "Rescale" of the map (so you see something like 16/400%), then map zoom may not look the same in web Google Map...

[john_percy]

@menion
No rescale whatsoever. Google size isn't the same as the referring Locus one.
Using MF4 map of GB, zoom 14, 15, 18 sequentially; Locus then Google:


It seems to me that Locus needs to send a lower zoom value to Google, probably based on the resolution of the device.

Edit: I tested hard coding a zoom level into the www bookmark, and much to my surprise the areas matched exactly for MF4 maps on that zoom in Locus on my device. That seems to indicate that {mapZoom} isn't sending the correct value. For Lomaps/MF3, there remains a mismatch.

[tapio]

Menion could implement basic maths there, but sounds like overkill.

Problem in stable, I already deleted Cache of Locus via its preferences. I see it almist dayly, after exit Locus and restart Locus mostly all icons are white again. Anyone else? See attachment.

Menion, with low FPS I mean, the map movement or scrolling feels like micro stuttering. Or as in gaming, low frames per second, i. e. as if 10 pictures per second are displayed. As I said, only in a few dialogs...

[Menion]

@john_percy
sorry, but I do not know what to do with this. There really is some problem with the correct value, but not sure if this is an issue on the Locus Map side. It is a little problematic because of some automatic rescaling that Locus Map does on the background to display all maps with the "same" resolution.
So agree, zoom value does not work perfectly, but from my point of view, it is a too minor issue to spend more time on it.

@tapio
problem with the color of icons: same with the latest Beta version?
low FPS, understand, thanks. Same with recent Beta version and same with non-vector (any online for example) map?

[tapio]

Color in icons, will observe, have only seen in stablem.

FPS. I made an interesting observation, which has always been like this, I remember. I recorded it but can only upload in a couple of days. Happens in beta as well.
Edit a waypoint, then tap the circle/dot in order to choose a new position. The newly opened window is "nervous", like shaking or shivering, for maybe 1 or 2 pixels of distance. Vertically. Very subtle effect. If I then tap "from map center", the new map overlay window will be low fps.
But when I e. g. drag down the Android menu from the top, then put it back up, so Locus window re-appears in full glory, the shivering is gone. And then, the map window moves fluidly.

Huawei device, 1080x2244, Fullscreen Locus.

Edit.I checked the Favourits/App picker and I can definitely say, whenever the window is shaky, it scrolls badly. When it's stable, scrolling is smooth.

[tapio]

Action map_zoom with fixed value seems defunct. Zoom+/- works.

tasks: { map_zoom: { action: "16" } }

[Menion]

Tapio, this low FPS problem is really something very specific to your device. I'll ask Petr next week in office to try this on his own Huawei P20 device, hopefully he will have the same issue. Anyway because there is a really huge number of users and you are first who write to me about it ...

Map zoom: sorry, docs were not precise enough. Check please updated doc with a small sample: https://github.com/asamm/locus-api/wiki/Action-tasks-(Broadcasts)#map_zoom

[tapio]

Thx, zoom works, but weird numbers. "24" is zl 16. Low numbers soon show the whole earth.

As for fps, I can add: it happens only if app uses the notch area. I will of course still use the notch area, because the issue is tiny.

[tapio]

For the completeness: Here you can see the nervous window. You cannot very well see the stuttering map scrolling, in reality its more noticable.

https://youtu.be/SrZHkqDR3Nw

[tapio]

Menion, could you please include data/interpolators into the backup? Definitely a small set of files.