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 - Viajero Perdido

Pages: [1] 2 3 ... 7
1
Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: Yesterday at 21:46:22 »
Just checked again.  I turned on ~21,000 geocaches in Canada, then zoomed into a Hong Kong offline map, where only 3 personal waypoints are shown, nothing else nearby, and POIs are turned off as well.  Result: lag, can lift finger before it reacts.  A small but noticeable fraction of a second.

Then I turned off (hid) all those faraway Canadian geocaches.  Result: Hong Kong is nice and fast, very responsive!

Then I enabled "POI grouping".  Same result, both cases.

I assume this might be triggered by LoMap POIs too...

2
Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: July 17, 2019, 18:23:11 »
Hi.  Apologies if this was already discussed up-thread or in another language.

3.38.7 is really laggy when panning the map.  For a typical swipe-to-pan, you drag your finger across the screen, but the map doesn't react until after you've lifted the finger!

Psychologically, it sucks the energy out of exploring the map.

This happens with LoMaps, OAM V3, and OAM V4, on my low-DPI phone, also the high-DPI tablet.  Scrolling elsewhere, eg in the geocache logs list, is normal and responsive.

Is there a drag threshold that's set too high?  Is this something I can adjust?

EDIT:  Ah, I suppose I could turn off some of the ~15,000 geocaches I've got visible.  Trimming that down to ~4000 (my local area) made all the difference, performance acceptable again.  (The others were far outside the area covered by the current view, so should they have made a difference?)

3
First off, a big thank you for updating G4L for the new API.

I did find one glitch with 3.0.0.  When you "Download logs" from the Locus share menu, it also downloads log image thumbnails as usual, but in reverse order.  For example, my two logs on https://coord.info/GC2ZTTK .  (I assume it's G4L handling that.)

Sometimes you like to tell a story with the pictures, and are careful to upload them in the correct order.  Groundspeak then displays them in that same order on the cache page.  But for now, G4L inserts them in reverse order.

I trust that's a simple fix.  Hope so.  Thanks.

4
Looking even better with those tweaks, thanks!

Are unsealed roads actually drawn wider than sealed ones, or does it just look that way?  They seem quite prominent.  (They do serve to point out where I've mapped wilderness highway=unclassified and forgotten surface=unpaved, oops.)

5
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 05, 2019, 18:05:36 »
Importing of PQ files should finish on the map I think.
Sounds totally reasonable for most use cases.

My use case is probably less common, 7 PQs into this folder, 6 into that one, and so on.  Different folders, so different import steps.  But it's only an extra couple of taps, so I don't mind.  I mentioned it only because it seemed to be acting inconsistently.  Anyway, thanks!

PS, my opinion on slope shading:  I wouldn't lighten it tooo much.  At lower zooms, shading nicely takes the place of topo contours - which presumably disappear at such zooms.

6
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 04, 2019, 22:53:47 »
I don't understand Zoom Lock.  In the beta I've assigned it to the lower-right button, and tapping it toggles between 12 / 100% and 12 / 1600% (or any other number in place of 12).

That's not intended, is it?

If it is supposed to work that way, maybe it needs another name.

Ah, I get it.  It's kind of an "alternate zoom".  I can choose 100% and other%, and toggle.

7
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 04, 2019, 17:59:53 »
There was a temporary glitch with loading Pocket Queries last night.  This happened on two devices (one with Beta, one with Pro), but did not happen on a third device with Pro.  The problem was repeatable for a few minutes until suddenly it started working again.

Geocaching tools -> Load Pocket Queries
[thinks for longer than usual]
"Whoops! [very strange message and code] code: 429

Of note, I have 21 fairly full PQs available right now.  And that funny text before the "code: 429", I'm not sure that's even ASCII.

Whether this is a potential problem, you can judge better than I.

Also, in Beta, after successfully loading some PQs (no "Whoops"), I noticed it sometimes returned me to the map, sometimes returned me to the Geocaching Tools screen.  (The latter is more convenient, for loading the next set.)  Haven't yet figured out what I might've done differently.  (Dragged my finger on the screen to keep it from going asleep while processing PQs; would that change anything?)

8
I'm starting to really like your desertV4 theme.  Thank you very much!

There's a local urban road, highway=secondary, surface=asphalt, that appears to render as unpaved (dashed line, yellow / white).  The adjacent secondary road with no surface tag renders as solid yellow.  This is with a current OAM V4 map.

And one more suggestion for outdoorV4, if I may.  At Z14, highway=path is rendered, but highway=track (a larger path) does not.  I'd suggest rendering track at Z14 as well, because it looks odd to see paths but not tracks at that zoom.

PS, the road junctions look great in outdoorV4 now.  Thanks.

9
Hi.  Thanks again for the quick response.

I gave both outdoor and outdoorV4 a try, but see nothing different about road junctions.  I've noticed the .xml in both zip files is dated a few days ago.  Did you possibly forget to upload the latest?

I see you've fixed the bridleway glitch, thanks.  But I've noticed now that some mixed-use trails, ones for both cyclists and walkers (such as the one beside the bridleway I mentioned), no longer appear unless you've selected "cycling lanes".  This happens with trails tagged highway=cycleway, foot=yes.  (There are multiple ways to tag such mixed use, and I think my city has them all.)  I'd suggest walking trails *always* be visible, given the name of the theme.  :)

10
Thanks, and thanks!

It's hard to describe, but a picture is worth a hundred of my words.  This is from V3, but I think V4 is the same.

Currently, the ways look disconnected, as if one crosses above/below the other.  (Notice also the junctions of alleys to residential in the same image.)  I think the style on the right is how it's more commonly done, and what my eyes expect to see.

Thanks again, VP.

11
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: April 29, 2019, 18:09:42 »
My apologies, I should have mentioned how to activate "tilt", rather than just leaving it as a mystery.

I was experimenting with zoom lock (after seeing it mentioned here; never used it before), and managed to get Locus into an endless rendering loop.  This is with an OAM V4 map, new "active RT4" theme, zoom lock on, but can't remember original zoom level.

The screenshot also shows, incidentally, the old glitch of not rendering areas with no content, those big rectangles.  But here, in a loop, Locus would render the screen as shown, then grey out the entire map, then render again as shown, repeating indefinitely.  It's a slow-moving loop, a few seconds each time through.

No idea what's going on here.  Maybe this is one of the problems with tilt that Menion mentioned...  EDIT: Removing tilt doesn't stop the loop, just speeds it up a bit.  :)  Turning off zoom lock doesn't stop the loop either, but then choosing a different zoom level does finally stop it.

12
I really like the Outdoor theme, so thank you, especially for adapting it for V4.

If I can offer a few suggestions...
  • For some reason, highway=bridleway renders abnormally large.  For example, at N53 31.484 W113 32.897 on the OAM Alberta Canada V4 map.
  • Certain highway types, where they meet (eg, residential x service), are drawn such that they appear to be unconnected.  If you were to imagine the ways as pipes, water couldn't flow through the connection.  That's sent me into OSM a few times to double-check the data. ;D
  • There's no checkbox for boundaries and protected areas.  Given that the theme draws the name on each tile, and Locus still uses lots of tiles, this can lead to a display rather full of names.  It'd be nice to have the option to turn this off.
Thanks!

13
Troubles & Questions / Re: Data Transfer In Android Phone
« on: April 27, 2019, 20:51:16 »
A file manager app.

"FX" is good.

14
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: April 27, 2019, 18:06:32 »
I really like the "tilt" feature.  But I suspect more people will accidentally activate it, then wonder how to reset it back to normal.

Maybe it could be a simple on/off setting, and in the UI beside "Rotate Map"?  (Then I'll know I've got it tilted the maximum; I'd never want it half-tilted.)

I can't repeat it now, but for a while, there was an unwanted panning of the map, after I turned the power off then on again.  This was both with screen lock active (swipe up to unlock), also controlled via "basic screen lock" disabled.  It looked like the swipe-up-to-unlock was being caught by Locus and used to pan the map, but then I saw it happen with screen lock disabled too, no swiping.  And now it's behaving perfectly...

15
Discussion/New features / Re: Update of map core (2019)
« on: April 26, 2019, 20:58:40 »
I think the latest version is now the freshly-released beta (via the usual beta channel), which would render the alpha obsolete.

Haven't tried it yet.

Pages: [1] 2 3 ... 7