Problem with "Automatic zoom" together with "Magnify all maps" in 3.38

Wolfgang shared this problem 16 months ago
Solved

I think there is a problem in 3.38: "Automatic zoom/Zoom according to speed" doesn't work together with "Magnify all maps" correctly. I set "Magnify all maps" to 150% and I set Automatic zoom to 18 at 0 km/h and 10 km/h. As a result, Locus set the zoom value to 17/200% in the map(?)

In 3.37 Locus sets the zoom value to 18/150% - that's what I expect in 3.38 too.

With "Magnify all maps" deactivated Automatic zoom seems to work correct in 3.38

In addition: The dialog to define "Automatic zoom/Zoom according to speed" was better in 3.37. In 3.37 I could see the actual zoom/% value in the display. And 3.38 shows % values in the list of values - I think the % value is unnecessary because it's set with "Magnify all maps" and should not occur in the list of values in "Zoom according...".

3.37.2:


3aec271916ba8ce6652d4ecfa47f750e


3.38.3 Pro + Beta:

2890fa3a2e7a4d95af808e6dc3263edd


3.38:

179aa51657980ff88fa86dc99e92e564

Comments (5)

photo
1

Hi Wolfgang,

have you tested this on the newest Locus 3.38.4.?

Michal

photo
1

Yes, just 1h ago. Still the same.

photo
photo
1

Good day Wolfgang,

seems I have to get rid of these numbers completely. They are not anymore precisely describing the final zoom value set during movement.

I'll look and it and try to improve this to next Locus Map version, thanks for bug report.

Menion

photo
2

Hello Menion,

I think you should try to stay with these zoom-numbers somehow - just to be able to communicate and to refer to something like zoom levels.

In my opinion it makes some sense to be able to refer to zoom levels e.g. in the definition of "Zoom according to speed". In the definition I would suggest to use the zoom levels (e.g. between 18 and 14) but not the % values in addition in this definition - like in 3.37. This should be fine enough to define auto zoom.

In addition it should be possible to define "Magnify all maps".

Even if you calculate internally with long (64 bit) or even longer... - you should try to calculate something like zoom levels and % according to magnify... values for the communication with the user. I think it was ok in 3.37 to use + and - zoom to switch between the zoom levels with the fix magnify % values.

I see your point calculating values back from an actual dynamic zoom value (not level) displaying the map during movement e. g. in auto zoom or when zooming in the map with a gesture. I hope you find a way to calculate/to show values for zoom level + magnify % similar to 3.37

Wolfgang

photo
1

Hello Wolfgang,

In next (Beta) version, setup of auto-zoom will be improved little bit. I have completely replaced zoom values (numbers) with small scale bars. I am not perfectly satisfied with it, so some feedback will be welcome.

photo
1

Hello Menion --

Sorry for the delayed response; I did not notice this change until I had occasion to change some Automatic Zoom settings.

I had the same problem with Automatic Zooming and Magnify All Maps, so I am happy to see an approach which accounts for both. However, I have encountered some problems in the "Automatic Zooming" dialog:

1. Adding a new ZOOMS entry seems unreliable. Sometimes it works as expected. Sometimes after SAVE, an existing entry has disappeared from the list, or has had its scale value replaced. Tapping (+) and then BACK/CANCEL makes the missing entry visible again (with its value replaced).

2. I find the scale bars for Automatic Zooming confusing. The list of scales shown by the map display (-)/(+) buttons, by the Automatic Zooming (-)/(+) buttons, and by the ZOOMS list are all different. This makes it hard to calculate what settings to select, and hard to note down the settings in case I need to restore them. For example, if I want to use scale 16 as a zoom level, the map display shows a 0.5 mi scale bar. The closest Automatic Zoom selection (without pinching) is 0.6 mi. Adding that as a ZOOMS entry shows a 0.4 mi scale bar. Similarly, map scale 18 shows scale bars of 700 ft, 800 ft, and 500 ft, respectively.


019c37f73000061e32d14a0e84e67628


2dd93d71239228083984bb9353ebfa2d


Ideas:

a) One improvement would be to have all three places use the same set of zoom increments and scale bar lengths. Then it would be easier to calculate what settings to select, and to note down the settings in case I need to restore them later.

b) I view scale bars as a holdover from paper maps. They require ruler measurements and math in order to figure out distance on a map. That seems anachronistic on a computer which can do graphics and calculations.

What I would REALLY like to select from is the viewable map size (width x height). For example, if I want the map to show about a half mile ahead and half mile behind when walking at 3 mph, then I should be able select something like "Map Size 0.5 mi x 1 mi" to add to the ZOOMS list. The Automatic Zooming preview display could show the view size dynamically, perhaps replacing the scale bar, or perhaps as a rectangle with two sides labeled.


af5f1d19aad298e275bedbf12577354c


Or alternatively, something like:


b1115f9364ac52bb9103560e77ff3522

The size of the viewable area should reflect the current Magnify All Maps setting and the hardware screen size. I have been doing such calculations in a spreadsheet, based on ruler measurements of screen and scale bar. It would be much nicer if Locus could do that for me.

Thanks for keeping up an outstanding app,

-- George Snyder

photo
1

Hello George,

thanks for the suggestions.

1. you wrote "sometimes" > please try to find exact steps that lead to any problem

2. issue with scale bar > we try to move away from exactly defined values, like visible area like you suggest. Core method to setup optimal values for auto-zoom is the top map, so please use it. Just tap on the existing line with speed & scale and map should change it's zoom to defined value. With this, you may clearly see what zoom is set for which speed.

Scale bar is currently generated automatically based on the available space on the screen. Keep it more united may be useful, agree.

Menion

photo
1

I think I have the editing problem (1) narrowed down. It occurs if the ZOOMS list contains an entry for speed zero. It looks to me like the (+) button creates a "blank" ZOOMS entry with speed zero and the current scale, and the [SAVE] button fills in that entry's values. Unfortunately, if there was already a ZOOMS entry for speed zero, it gets overwritten. To demonstrate:


1. Edit a Preset and Open its Automatic Zooming dialog.

2. Add a ZOOMS entry for 0.0 mi/h:


2cf449dac64e0b94d9d2e11832c9f9d0


3. Add a ZOOMS entry for 1.0 mi/h. The 0.0 entry gets replaced:


e7c31c5f3bdede908326749b12297e11


If I watch closely after tapping (+), I can see the 0.0 entry being created or selected just before the virtual keyboard pops up. Tapping (+) and then [< BACK] (cancel) just creates a new 0.0 entry with the current preview scale.


Workaround: If you need an entry for speed 0.0, create it last. If adding to an existing list which has a 0.0 entry, you can temporarily change it to some other speed, then restore its speed when finished.


Using Locus 3.49.0 on Samsung Galaxy S9, Android 10, Kernel Version 4.9.186, Security patch level September 1, 2020.


-- George

photo
1

Hello Menion --

Even with the current scale bars, I think an indication of resulting map area would be very helpful for setting up a ZOOMS list. The rectangular indicator I showed above is essentially two scale bars. It could use essentially the same calculations as the existing scale bar, but with different parameters (physical display size and rectangle size).

f6a7152684b373ae6f1a41f93651a87e

-- George

photo
1

Hello George,

thanks for your investigation and new info ;). I was playing with this feature for a while. How it works, it is an intent. From certain point of view, it make sense. Anyway agree, it should work better, more logical. I made some updates in behavior how new values are added, so give a try next version 3.50 (during November).

Idea with visible rectangle ... I understand your point, but I really do not want to add something like this into app. Scale bar was added instead of zoom values (that were visible before), because I wanted to get rid of some "crazy" text values. Thanks for understanding.

Menion

photo