Messages

The .5 beta doesn't fix it, I'm afraid, but thanks for suggesting.  Both scenarios, with- and without G4L visible, still cause the problem.

But I see the cache-info panel now appears at the bottom, not side, which is nice because I can swipe that one away, not the side version.

Looks like the cache owner is at fault here, for specifying "cursive" as a backup to Comic Sans MS.

It doesn't surprise me that the Microsoft font isn't available on the phone (it might surprise the CO), and obviously Android provides a font to satisfy "cursive" requests.

[unresponsive]

Hi.  I've noticed something unusual recently, maybe since downloading my current 4.15.2.  If I interact with G4L from within Locus (eg, double-tap the map, tap the G4L icon in the panel, do anything with G4L or simply try to dismiss), Locus becomes unresponsive to the touch.  (The panel does auto-hide, so it's not fully locked up.)  I need to task-switch away then return to Locus, which now works again as usual.

This happens on my Android 13 tablet, but not the Android 9 phone.  Locus is not running as a service, Screen on/off control is disabled, Always screen on is disabled, Unlock the screen is enabled.

PS, this also happens when I bypass the G4L UI, eg via "Update cache."

Thank you!  First impressions are, I like it.

Oddly, I can't get it to appear in the themes list on my Android 13 tablet.  This is with Locus configured to use the /media/ path, and I even tried unzipping, also tried putting a copy in the /data/ path, even through that folder is otherwise empty and unused.

But it does work on my Android 9 phone, which is set to use the /data/ path, by simply dropping the same .zip into the usual place there.

That might be a Locus issue.  I can't see anything wrong with your theme, and other zipped themes adjacent to this one are showing up in the list just fine.  I tried restarting Locus, clearing cache, nothing helped.  But on the phone, it just worked, instantly.  Both devices are running the current non-beta Locus 4, with the same current OAM V5 maps.

[an easy way to find public photos]

Clearly I suck at communicating. 

I was trying to suggest an easy way to find public photos ... by having them indicated on the map.

(Tapping every POI is not an easy way.)

It's not exactly what I was thinking of, but I imagine it'll help, thanks.

I was suggesting some sort of indication on the map, such as a modified POI icon (or maybe a tiny camera icon superimposed) via an online query, to indicate there's a photo available, tap to see it.  Use case: browsing a new area to learn about it, oh - picture!, tap to see.

This wouldn't help me specifically, but should enhance usability of the new POI-photo feature, and encourage people to use it.

Thanks.  Actually it says, "Custom directories are no longer supported" on my Android 13 tablet, but it's moot because I have no need to use that (old) feature.

I was hinting that (1) for this new feature to be useful, there should be a way to see "Photos" pop up noticeably on the map, and (2) that it takes a trip to Help to realize that "Geotagged photos" isn't the way to do it.

So...  There's no way to see which POIs have new-feature-photos, other than by tapping on them?

Hi.

I've uploaded a handful of photos to POIs using the new feature, not sure of the exact term, and they were accepted.  They show up when I tap a POI icon, as expected.

But when I turn on the "Geotagged photos" layer (and turn off the POI layers), I'd expect to see an indicator of where there are photos such as mine.

Without resorting to the Help, I have a sense "Geotagged photos" refers to something else, an older capability somewhere in Locus that I don't use.  But...  those photos I uploaded are technically geotagged ... no?

I think those photos need to be more discoverable ... somehow.

For geocaching support, there is only one choice.

No worries.  I think of Cloud Sync as my primary backup, and that works so well, I rarely care about "backup". 

I have the same problem as Graf Geo mentioned in #2 above.  This is on my Android 9 phone where Locus/backup is under Android/data/...  I don't do cloud backup (but would, if I could use Proton).

[Web]

I'd like to try out the photo-upload feature.  But first, I need to scrub my real name and use my internet name instead.

BTW, the blog post at https://www.locusmap.app/hows-it-look-in-there-anybody-got-a-picture/ says the user profile is only accessible in the "Locus Map application".  I think you meant to say, "Locus Map Web application" because I couldn't find it in the Android application.

Anyway, I changed my user name in the web application, and it now shows my internet name in the corner of the map display, good.  However, on either of my two main Android devices, when I try to upload a photo, it still says "[my real name] will be published...".  (4.12.2)

My real name is unfindable on the internet, and I like it that way. 

EDIT:  If I then visit Locus Store, Account, I see [internet name] and icon that I chose in the web app, good.  THEN, when I try to upload a photo, it correctly says "[internet name] will be published...".  This happened on both devices.  A visit to Locus Store / Account was needed for it to correctly show the desired name.

I would clear your temporary data (Settings / Miscellaneous) after moving SRTM files around, because I expect Locus might cache a rendered version of the shading at different zoom levels.

But I'm just guessing, and the author is right here. 

BTW, my main area of interest - eastern BC - is double-covered by OAM's AB and BC maps.  There's significant overlap where AB's map is well outside the borders, big enough to cover entire vacations.  But I'm grateful for the overlap because the BC map is huge, and I don't download it often.  So I have older BC data, and the freshest AB data, for the same large area.  (And I don't know what the auto-chooser should do.)

So that's perhaps a more real-world example. 

I can live with it.

PS, if Menion wishes to look at this, I have a hunch the accidental doubling of maps also occurs if you have two maps of the same type and region, but from different dates.  I routinely rename my OAM maps to include the month/year of issue, and keep an older copy or two in my unit (... so I can debug unexpected changes to the data).