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 ... 8
1
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.

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

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

4
Versions / Re: [APP] - version 3.40.+ ( 2. 10. 2019 )
« on: October 09, 2019, 00:15:40 »
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?)

5
Versions / Re: [APP] - version 3.40.+ ( 2. 10. 2019 )
« on: October 02, 2019, 21:30:09 »
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.  :)

6
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: September 29, 2019, 16:53:54 »
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..

7
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: September 26, 2019, 19:05:38 »
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.)

8
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: September 20, 2019, 18:23:03 »
@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...

9
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: September 19, 2019, 22:03:42 »
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.))

10
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: September 18, 2019, 18:37:48 »
Below is not just in beta but pro as well...

if the export directory is invalid, and then long tap on a track, then tap Export, an orange msgbox is displayed with the correct problem, BUT only for a very short period, 100ms.

Also happens if you're exporting to an online service (OSM in my case), and you're in airplane mode with no internet connection.  Stupid mistake on my part.  (I mentioned this over on the help desk, with a different root cause; root cause was fixed, thanks.)  Once again, I needed to record a video with my camera, and step through it frame-by-frame to read the message.

(The error message, in orange, is behind a green "Process successful", which isn't true.)

11
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: September 05, 2019, 22:11:24 »
I have some feedback on the new built-in GPS Averaging feature in beta 3.39.4.2:

First, the really obvious glitch.  My true coordinates are N53 W113, but the averaging screen shows S113 E053!  N/S are switched, E/W are switched, and even the order between the two numbers is switched.  Oh, and there's a leading zero that's not needed.  Also, it shows a distance of almost 14000km, which I assume is half the circumference of the earth.

But more importantly, there's an issue that's been around for years.  Once you tap Confirm, you're back at the point's Basic Info screen, with correct coordinates.  But the altitude is not what you just measured.  It appears to be SRTM altitude, but who wants that number when you've just measured a more accurate one with GPS?  And "Get" is ambiguous; what does it do?  (My best guess is, fetches SRTM altitude again, if not already known.)

Occasionally I like to measure peak altitudes for updating OSM, but have to remember to record the altitude separately because I can't trust the built-in field.  (Can't trust because it's ambiguous, and the number is different than I expected to see.)

Also, the choice of "GPS Averaging" as the name could cause confusion, as it's the same as the name of an external app doing the same function.  Since "My Location" and "GPS Averaging" are similar concepts, maybe you want different names such "My Location - Quick" and "My Location - Averaged"?

And one time only (first time), when I tapped "Get", the app disappeared.  A few times after that, no problem.

PS, it's a great solution to the problem of the external app having become malware.  Though for my own use, I managed to find an old good copy.

12
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: September 05, 2019, 04:18:56 »
@Viajero Perdido
"Rockies": enjoy it and send us some photo from the field tests, so we have some kind of "nonworking" post here :)

Since you asked, how can I resist?  :)

I never knew grizzly bears came in white!  Shot from the porch of the Stanley Mitchell Hut in Yoho National Park, at close range.  This bear and its normal-colored sibling came around twice during the day.  Amazing to see.


There are a few more pictures in my geocache log here.

Sorry, I have no field test results.  I only carry Pro in the field, after some confusion in the past with G4L getting confused between two Locus versions (Beta/Pro).  But I eagerly await the next Pro version with the labels fix, thanks again.

13
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: August 24, 2019, 15:02:10 »
As others have mentioned, the .3 beta seems to have fixed the cut-off text problem, even with magnified (200%) text.  Thank you!

I think I might have seen one text label disappear as I panned it into view, but that might have been a brain problem on my part (coffee not fully absorbed), because I couldn't reproduce it.

But essentially, I consider this fixed.   8)

I'm disappearing into the Rockies now for a week and can't reply to anything, sorry.

14
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: August 19, 2019, 21:13:23 »
Magnifying the text of offline maps seems to increase the likelihood of labels being truncated.  I usually do 150% where it's fairly noticeable, and at 200% it's quite noticeable.

15
Versions / Re: [APP] - version 3.39.+ ( 25. 7. 2019 )
« on: August 19, 2019, 06:41:05 »
Text labels are still sometimes cut off at tile boundaries with Beta 3.39.3.1 when using OAM ML V4 maps.  LoMaps (which are still V3, right?) seem fine.

I asked earlier if there was a secret "hack" way to force V4 labels to render properly.  That's because I noticed that when you see a cut-off label, you can zoom out one notch, then in one notch, and it renders properly.  I'd thought, maybe there was a software hack to internally do the same thing, or something like it.

I don't remember what the advantages of V4 are, but I know this is the disadvantage.

Pages: [1] 2 3 ... 8