Messages

[fzk-outdoor-soft-v5]

This is a coincidence.  In the last 48 hours I discovered:
1) I really like the fzk-outdoor-soft-v5 theme, because it shows useful roads at low zooms in remote areas.
2) It doesn't show highway=track, meaning I can't use it; I need to see tracks.  Actually, none of the themes in the family seem to show them.

So I edited my copy of the .xml, and pasted in a block of XML from the Outdoor theme, XML that deals with tracks.  Now it shows tracks, and I'm happy.  I was thinking I should mention it; a bug?

I'm using OAM V5, but as I recall, the tracks were also missing using the latest LoMaps.  I had turned on all the theme options.

EDIT: I spoke too soon.  My hack-fix didn't catch all types of highway=track; some are still invisible.  Back to the text-editor...

(Sorry if I've taken this off-topic, but since you mentioned the start-up work...)

I forgot to mention, it seems to only take a very long time after starting up the tablet for the first time; I keep the old thing powered down except when prepping for a camping trip.  So, charge and power up the old tablet, then start Locus 4, and it takes 10 minutes, maybe closer to 5; I haven't timed it.  I can tap "Wait" a few times, or just let it sleep and I come back when it's ready.

The progress shows it's slowly loading the 10,000's of points I have, one group, slowly the next...

I'm about to give up on this old tablet for other reasons, so it doesn't really matter to me.  But I will give it a try after a while, just out of curiosity, and report back if I don't forget.

EDIT: Yesterday I powered it up (after charging from dead), and just now I loaded LM4.  After seeing the 4.18.1 upgrade message, I pressed Next, "not responding", Wait, and... it started fully within seconds!  So the problem is either gone with your upgrade, OR it was a case of Android being extremely slow in the first few minutes of its life, while I was also waiting for Locus to start.  In this case, those two things happened a day apart.

In other words, you can probably ignore this bug report.  Cheers.

I'm currently working on a new system for initialization of the app so I believe, this issue will be solved as well.

Good to hear.  Init is currently quick on my daily-use devices, but when I pull out the old Nexus 7 (2013) and fire up Locus 4 (I take it camping, sync first), it takes around 10 minutes to start, not including sync.  A bit odd; I don't think the old tablet is *that* slow.  After I'm back from my trip, if there's a beta with the new init code, I'll try it out on that device.  Cheers.

Adapting to using LoMaps V4 (migrating from OAM, alas) is going well, but with a couple of glitches.  Lake names are missing with some themes, admittedly older themes, but beautiful ones.  (And I'll miss OAM's placement of the name for multiple lakes or similar things, grouped in a relation, once in the centroid of such areas, rather than once on each lake.  Hint, hint.)

But the main reason for this post is to mention a funny difference between landuse=forest and natural=wood, at ZL=9 only, with LoMaps V4 and the internal hike-and-bike theme.  At ZL9, it renders wood but not forest, which makes it the only map I've ever seen that makes a distinction.  Many mappers and most renderers consider them equivalent, as it's something of a gray area.  So Alberta is a bit of a mess at ZL9, between old imports (wood) and my additions (forest).  First world problem. 

[lake names]

Thanks for mentioning the Tapiola theme; I wouldn't have noticed it.  First impressions are good.

I tried out the new V4 LoMaps too.  One thing that bugs me is: none of the OAM (V4/V5) themes in my collection, including this new one, show lake names.  It seems only Locus internal themes show lake names with LoMaps V4.

I may have to switch to LoMaps (depending on the fate of OAM), and would be stuck with a greatly reduced choice of themes if I want to see lake names ... which I consider essential.  Is it practical to fix this?

PS, I like how OAM handles lake (or similar object) names.  If multiple lakes share a common name in a relation (name=Pretty Lakes, example), it draws the name once at the centroid of the relation.  This is tidier than drawing the name on each of the (sometimes many) lakes, IMHO.

I was browsing the Locus website, and thought the picture at the top of https://www.locusmap.app/voucher/ looked familiar:


Yes!  It's a cache-studded trail in Hong Kong.  It was a great day, roughly a dozen caches, starting beside the dam down below, and finishing at the summit of one of Hong Kong's higher peaks.

Matching pictures:
https://www.geocaching.com/seek/log.aspx?LUID=98c41d85-f98b-4aa1-92e1-5312afa3ac82&IID=dc1e08b4-09f6-4e5b-806a-d991ee75df06
https://www.geocaching.com/seek/log.aspx?LUID=b652def7-93ff-4689-912a-afe28f81f138&IID=69a9c15c-7ca7-4d18-9c4d-afe1b94fbbff

In the current non-beta LM4, I can't find any themes in the store.  (I answered a question in another thread related to themes, so I was curious.)  I spent some time in the store totally lost, then found the "+" icon at the bottom of the theme switcher, which brought me to an empty page on the store.

This doesn't bother me personally, as I already have a nice collection of themes, which I scrounged from various places.  But it brings up a suggestion:

Once things settle down with the V3-V4 transition, there's a real need for a central place to find themes.  Not just supported themes, but even obsolete ones that still kind-of work; I sometimes still use Waymark because it just looks good.  I often use Outdoor/Desert*, same reason, but who can find those themes?  Even Voluntary, which jumped the hurdle to make it into the store, is no longer there ... or at least I can't find it.

(* To be clear, these are not obsolete, and fully deserve to be in the store.)

That happens with certain themes.  When I see that, I try another.

Have you tried the Elevate theme that comes with OAM?  It's well matched to the underlying map.

EDIT: on quick investigation, I'm guessing you're using one of the Locus internal themes with OAM.  The internal themes match well with LoMaps, but not so well (IMHO) with OAM.

Elevate, or any of the other V4/V5 themes (a bit hard to find), should look much better.

turn off GPS, so cursor position is used

I hope this is just a workaround, not by design.

When I'm standing in one place but the cursor is at another, my attention is at the other place, and I'd like the search / weather forecast / whatever to be at that location.  Just my opinion.

[@Viajero Perdido]

@Viajero Perdido
did you tried to press the device's "Back" button again? Maybe there is an "invisible screen" that needs to be dismissed again. Anyway more and more reasons to get rid of G4L. Just one cache by gc-code and live-map are missing...

Aha!  No, I didn't.

Just now, I duplicated the bug.  Then hit Back.  Responsive again!  And...  Now I can't duplicate the bug.  I think you're right, there was a hidden window that got activated along with G4L, and a single "back" was enough to make it go away, and stay gone.  Okay, never mind.   

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.)