Messages

[There are things covering up parts of the map]

PS, I had to think about why that prototype screenshot was bugging me...  Now I know.

There are things covering up parts of the map.  Four round things.  The map to me is #1, it's the reason for the app.  I have Locus set up to show a clean map rectangle, and all the cruft is outside of it, in panels where it belongs.  (Other than scale and invisible [!] copyright, but close enough.)

Also, I like BIG targets for the + and - buttons.  They're quite big now, but those fat round circles in the prototype look smaller and harder to hit, certainly harder with the left thumb.

My two euro-cents... 

With the two-finger zoom now default in any app I don't think the zoom buttons are needed except in particular use cases.

Disagree totally, sorry.

Two-finger zoom is a pain in the butt!  So is finding the hardware buttons.

If the on-screen zoom buttons ever disappear, I'll use an old version of the app in perpetuity.

I think I figured out how to duplicate the crazy-tiny text I mentioned above in #12. This is with 3.40.2.2 beta.

Turn on the magnifier, and pan around, using it to read street names at 100%.

In today's new beta, moving a geocache into position under the crosshair no longer causes a little summary window to pop up.

Intentional?

I kind of miss that, but could get used to it.  (EDIT: I do have "Labels on map" set to "On hover", so I guess it's a bug.)

Hi again.

"Nothing to download" happens a lot with the GC Offlinizer; many caches simply don't have any images.  I don't see anything unusual there.

I'll clarify my earlier comments.  G4L's "live map" feature creates temporary cache objects that aren't stored in any named folder; they can be expected to disappear soon.  I've never tried to "offlinize" a live-map cache and don't know what would happen; that would be making an expected-to-be-permanent change to something that'll disappear shortly.

If you want to "offlinize" caches, or manually make changes (eg adding multi waypoints), you should be doing this to permanently stored waypoints, eg in a named folder.  You can get caches into named folders by loading PQs, by bulk-downloading in G4L ("nearest"), or one-by-one using the copy-to feature from a live-map cache.

Hope that makes sense.    I generally do everything offline with PQs, which works quite well.

Sounds like you're trying to make a permanent change to a temporary geocache object, one brought in via Geocaching4Locus.  Right?

Try saving the object to a folder (effectively making it permanent), then modifying it.  Or simply switch completely to offline caching using PQs.

Here's a screenshot.  There IS actually a white border around the text, but it's very very thin.  Notice the "101" text in the lower right corner?  Even at this larger-than-tablet magnification, it's very hard to tell there's any separator.

BTW, I held the tablet - from which I took the screenshot - up against the LCD monitor on which I'm viewing this post, and the attachment preview shown below is only barely smaller than the matching image on my tablet.  So that preview is a pretty good approximation of reality, though of course at lower resolution.  This is why I need 150% or more.

Also, Locus beta 3.40.2.1 here is going nuts, drawing and redrawing the labels at two wildly different sizes.  Here I've caught a screenshot with both sizes shown at once.  Panning seems to trigger some re-rendering, and I had to pan a lot to line up things for the screenshot.

This is using a recent OAM V4 map with your latest (I think) Elevate theme.  Thanks for looking into this.,

I have to disappear shortly from the internet for a few days, sorry.

I'm using OAM/Elevate, same as @lor74cas.  I had a hunch readability was at least partly a theme issue, at least as far as text size and white borders around the letters is concerned.

BTW, I usually have my text size at 150%, which makes road names hit the borders of the road they're rendered inside/atop, black hitting black, which makes white borders around the letters a bit more desirable.

Thanks John for the very fast update on your theme!  I'll check it out.

This is indeed a big improvement - congrats to all involved!

There's still a wish-list, though.  (Isn't that always the case?)  A few items come to mind:

• Trails often turn sharp corners, and text suffers when bent sharply.  I wonder if there's a way to avoid rendering text around sharper corners somehow...
• Text looks to be rendered with a very thin white border (1px?) around the letters.  Barely noticeable without magnification.  I'm thinking a slightly thicker border might be more readable.
  
• And...  (unrelated to the latest change).  Divided highways often render the same name twice, once for each direction, overlapping and thus barely readable.  If the code has collision-testing logic (does it?), it could check to see if the two colliding texts are identical, and if so, could render it just once at the midpoint between them.

I'm tempted to pull down the MF code and see if I can't get involved personally on this.  But in reality, that'd have to wait a while, and for all I know, the MF developers may already have a solution for some or all of this. 

Anyway, that's my dream list.  Thanks for reading.

Can't be sure, but it seems I'm seeing more texts being cut-off again.  Is this a by-product of the speed-up to map rendering in .2? 

(Or to rephrase, was the "fix" to the text problem an intended byproduct of extra rendering done in 3.40, now removed?)

On both my daily-use devices (Android 6 & 7), after installing 3.40, Locus was gone from the quick-launch panel at the bottom of the home screen.  (It gets the premium corner spot.)

Minor but interesting.  It was easy enough to put back. 

I've spend almost two days on speed up of the cold start itself.

Holey moley, that's fast now!  No problems seen with RC2 on my Android 6 / Nexus 7 with its motley collection of maps, points, etc.

It was only a quick test, all I had time for.  Cheers..

Trying the RC...  I'm okay with the lack of built-in GPS averaging, and it's nice to see the app still uses the external version if available.  (I kept a copy of 3.0 which is pre-malware.)

But best of all, after much couch-surfing, I see the issue of cut-off texts with MFV4 maps is almost completely gone, as I probably mentioned before.  It still happens, but very rarely, maybe 1% as often as it used to.

Map rendering does seem a bit slower, BUT as I think I'd said, I'm perfectly willing to accept that in exchange for proper map rendering; I'm guessing it needs to re-render some tiles to fix the text.  Also, I'm testing the RC on an older, slower device, so it's not really a fair comparison.  In short, speed is okay, rendering is wonderful.

LoMaps still seem to be V3.  Will they switch to V4 at some point?  (Sorry if it was mentioned somewhere; I haven't seen it.)

[@Viajero Perdido]

@Viajero Perdido
if possible, may you please try to test your map with the Cruiser application? I'm suggesting this because Emux who create Cruiser is current probably most active MapsForge developer. In case, same problem will be in cruiser as well (which I expect), it is more MF problem. Thanks.

Ah yes, the same thing does happen in Cruiser.  So I guess it's a MapsForge problem...

[name:en]

The old "en" problem seems to be back.  This is something I brought up a couple of years ago.  I mention it here because it might be related to the new MFV4 handling.

I'm using a brand new OAM V4 Multilingual map, because I like the V4 goodness with better label handling, soon to be even better yet with un-truncated text.  (I'm using the latest Pro, not beta.)   The map is Hong Kong in this example, and a good POI to illustrate the problem is a restaurant at https://www.openstreetmap.org/node/5977868688 .

Because the POI has name:en but no name tag, the restaurant name displays with "en" in front.  Note that I've manually selected English for this map, so there's no need to point out when it's a language I'm already expecting.

Hong Kong, like Vietnam that I'd mentioned earlier, is littered with POIs with this mix of tags, and thus prefixed "en".

(PS, the map I'm using is so new, it doesn't even show up yet on the main OAM download page.  I found it here.  EDIT: but you see the same effect with an older version.))