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 - slarti76

Pages: [1] 2 3 ... 11
Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 20, 2019, 19:46:32 »
*** Beta with a bunch of updates & fixes *** (not just problematic navigation).
Magnify now works flawlessly and as expected, didn't have any hiccups in (admittedly short) test. Thanx, great!

But I have one complaint:
Hiding the "world maps" from the Quick Map Switch is a NO-GO like this: I have a downloaded Google map with a wide zoom level range (7-21 or something) that is now hidden. It's my main offline map! Please don't hide maps that also contain high zoom levels.
Good opportunity to point to this again: - definitely the more flexible solution... ;)

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 14, 2019, 08:27:25 »
correct, I still believe current behavior works correctly. As I wrote, there is a need for one tiny change that causes a little trouble for me. If you set 150% to magnify, the app just needs to do zoom by this 50 % (like by fingers) and then all will work as expected. Anyway, let it be for now, I'll invest more time to it and in next Beta ...
It's slarti76 ;) Nevermind...
Tried out 3.38.4. First tried with 200% and 300%: Absolutely identical maps displayed. Then tried out 150%: No change between 100% and 150%. Then, as you hinted at, zoomed out and in again: Now it looks like it may be 150%. Tried out 200 and 300 again: Now there was a difference.
At last, tried 400%: Different to 300%, but muuuuch bigger.
Now I noticed the percentages shown in the top bar. At base resolution (no magnify), it showed "200%". Ok, probably a result of the DPI calculation, whatever. With magnify to 300%, it showed "500%" (which is 2.5x=250% magnification). At 400%, it showed "1000%" (which is 5x=500%).
No it struck me: The problem here is, I think, that my map doesn't have linear zoom levels, the highest levels are "1:50000", "1:25000", and "1:10000". I assume that when I'm in the "1:10000" level, that messes with your calculation, as you expect the lower level to have half the resolution (1:20000) and calculate the level to be used for magnification and the enlargement of tiles based on that - which has to fail.
With a Google map download done by Locus, I don't have those severe discrepancies, but there's also no difference between 250% and 300%, for example.
Also, when I zoom in more than the highest zoom level (one or two additional taps on "(+)"), I'll still get to a point where Magnify has no effect.

So in summary:
  • The algorithm seems to break down when the map's zoom levels are not 1:2
  • Magnifications between full 100% steps are sometimes a problem*
  • Magnifying when already magnified in highest zoom level doesn't work
  • Sometimes magnification is not applied directly, only after another zoom in/out
* I think it would be no loss to get rid of the 25% steps, and also all 50% steps after 200%, but at least 150% should work.

Hope this helps.

PS: Good news: Didn't have any blank screens anymore

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 12, 2019, 20:12:36 »
I'm still quite sure it works, it only does not immediately change what you expected (visible camera scale). Try to use hardware zoom in/out after you change magnify and you will for sure see difference.
Anyway blank screen with combination with zoom lock is weird. Can't simulate, but will be watching it.
Ok, I recorded a screen video, showing how it sometimes works, sometimes doesn't; plus an instance of blank screen when magnified. "Unfortunately", the factor worked in this case, but I did try it before with screenshots where the result was always the same no matter what factor I used. Can't figure out what was different.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 12, 2019, 09:24:07 »
Beta 3.2, "Magnify all maps"
The severe bugs from 3.1 are gone (no blank tiles/screen), but apart from that it's still not working as advertised. I'll summarize:
  • Factor has no effect, always seems to be x2 (vector and raster maps)
  • Raster maps: When in highest available zoom level at 100%, and I zoom in once, it enlarges to 200%. When I now switch on "Magnify", nothing happens. Things get even weirder when I use "Lock the zoom" - then I even get blank screens again. The current algorithm clearly doesn't work when in highest zoom. Probably also the case for vector maps, but there the highest possible zoom is so large that it probably doesn't matter that much. But with a raster map with max ZL17, it is!

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 04, 2019, 09:50:42 »
New Beta 3.1:
"Magnify all maps" totally broken for raster maps: sometimes screen is just white (downloaded Google Maps), sometimes it works, sometimes no change at all (still in highest available zoom level). Magnification level still makes no difference. For vector maps, it basically works, but also with always the same magnification.
Sorry, unusable. Restarted several times, cleared cache, just to be sure, but that's not it :(

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: June 03, 2019, 11:22:12 »
- during last days I've found a few more problems with maps, so you issue with OruxMaps may be the same, already fixed, issue.
Thx, but I think the real problem was what I wrote later about the magnifying: I was already in highest available zoom level, and then it didn't do anything, no matter what the (raster) map.

- the switch is in advanced settings.
Ah, I see the misunderstanding. It says "Optimize raster map resolution... based on dpi". I thought there was a switch to turn off the whole dpi concept, but I remember you don't want to keep the old system at all, so obviously no switch. All fine!

- the problem in route planner: this happens on both your devices? Seems you have some super-huge screen resolution, it is on your Note 4?
Actually, I could solve the issue with a "Clear Cache" from Android's App Info for Locus. Thx to Tapio, who mentioned possible caching issue - that seems to have been it. I think, whenever there is something wrong with icons, you should first clear cache. Can't hurt, anyway...

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: May 30, 2019, 13:56:15 »
Route Planner 3.38.3 almost unusable:
All actions on points (POIs, track points) are unavailable, see screenshot ("Add" is just a text, clicking has no effect).
Cannot confirm. On Poi it offers me 3 kinds of points to add. Maybe some icon cache related thing?
Perhaps. After restart, options did appear again for POIs and special points, but not when clicking on a plain track point. Weird...

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: May 30, 2019, 10:21:03 »
Route Planner 3.38.3 almost unusable:
All actions on points (POIs, track points) are unavailable, see screenshot ("Add" is just a text, clicking has no effect).

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: May 29, 2019, 18:36:16 »
Hi Menion
I think I now solved the "Magnify all maps" mystery:
  • The map doesn't get magnified when I'm already in the highest available zoom level. This kinda makes sense given the new system that uses the next zoom level and then enlarges the tiles. But it's confusing to say the least. I didn't notice this in the downloaded Google Maps, because it has more levels than my OruxMaps map.
  • The same observation also explains what John and I experiences: In fact, the magnification is not just 200%, it's the relation between the two levels. E.g., from level 1:50000 to 1:25000 it's 200%, from 1:25000 to 1:10000 it's 250%.
Now I'm not totally sure about your concept right now, but I have the feeling that you can't keep the current system together with a freely definable zoom factor. Either you go back to the old system, just enlarging the tiles by X% (and thereby changing the field of view). Or it becomes simply a "Magnify" switch that uses the next best zoom level, but same field of view. Of course, for the highest available zoom level (see 1), you'd still have to enlarge the tiles by a fixed factor, let's say 200%. But right now, the zoom selection is pointless.

EDIT: Well, it's probably possible to have both by choosing the lower zoom level and adjusting the zoom factor in a way that the tiles are enlarged just as demanded by the setting, while keep the field of view. Just some maths. ;)

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: May 29, 2019, 15:32:54 »
I still don't like the way "Magnify all maps" works. But I've also realised it doesn't respect the value in settings.
I can adjust the value to 150% in settings using the slider, but the map is actually magnified by 200%.

Sent from my moto g(6) plus using Tapatalk
I can confirm this, "Magnify" uses the same factor no matter what I select in dialog. Maybe this is also in relation to my problem with it sometimes not working at all...
That being said, at least I think raster maps do look better now when magnifyed.

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: May 29, 2019, 15:30:46 »
interesting problem with OruxMaps, nothing like this noticed but will watch it.
Thx. It actually happens again from time to time, but couldn't figure out the conditions yet. After switch to another map, it usually works again, but not all the time.

Notifications for updates are really weird. Yes, I looked on it and should be fixed, weird ...
Actually, now they're gone. It's possible, this time it was my fault, not cleaning the notifications. Sorry for false alarm.

One more thing: Can't find the switch to turn off map rescaling, at least it's not in Settings>Maps>Offline (I definitely saw it in the beta).

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: May 29, 2019, 11:19:02 »
38.3: "Magnify all maps" works again for OruxMaps maps, but weirdly only on second try (first time I changed to that map, the button had no effect, after switching back to another map and then back again, it was fine. So OK now.

Still getting notifications for map updates on every start. Did you have a look at that?

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: May 28, 2019, 09:45:36 »
Sorry, not planned for now. Understand that not all raster maps look same, but this fine tuning for the specific map will have to wait.

Also, this scaling does not change map tiles itself, so downloaded map in Locus will be exactly the same as with older versions.
Not sure what you're replying to? I'm still positive it's a bug that my OruxMaps raster map is not affected by "Change Map Resolution" while the ones downloaded with Locus are. It does work with OruxMaps map in 38.0, so something changed...

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: May 28, 2019, 08:05:50 »
PS: Ok, I tried a raster map downloaded with Locus, there Increase Map Resolution worked. But with an OruxMaps map, it doesn't have any effect. Anymore, still worked in 38.0

Versions / Re: [APP] - version 3.38.+ ( 22. 5. 2019 )
« on: May 28, 2019, 08:02:52 »
38.2: "Increase map resolution" is absolutely ineffective for raster maps. Doesn't matter if "Select map resolution automatically" is on or off. Also, the map resolution increment in all my presets was reset to 100%. Not that bad, as I have to find new best values with the new system anyway, but still...

Apart from that bug: I know it's more complicated, but all the problems with "Increase map resolution", especially for raster maps everyone seems to be having, I think the only feasible solution is to make this a property of the map. It's obvious that different raster maps look best in different zooms/resolutions.
It's nice and well that Locus choses the base resolution based on dpi, but then the user has to have the ability to adjust this according to reality and personal tastes.
I would propose that every map gets a "Resolution adjustment factor" from, say 25% to 500%. At least all offline maps. Then there's still the general "Increase map resolution" in settings/presets which allows to adjust resolution based on activity (e.g. biking needs more zoom because I look at it from further away).

What do you think, too difficult?

Pages: [1] 2 3 ... 11