Problem with two finger measurement

Wolfgang shared this problem 34 days ago
In Progress

Hi,

I have the two finger measurement activated. I know who it works. But mostly it doesn't.

I had the Map control style set to "Google" which one I now switched to "Locus Map" but there is no change. Measuring with two fingers only happens some times.

The problem persists since a long time. Years ago as I started with locus it did work.

The touch of my phone is working brilliant, and I try to tap with my two fingers simultaneously on the screen.

BTW 'map control style' what is the hidden menu. Nothing changes when I try to activate this.

Thanks Wolfgang

Comments (5)

photo
1

Hi Wolfgang,

to display "Quick measurement" it is necessary to keep fingers still for at least 750 ms.

I can imagine that this may be a problem during the walk, but if you personally stand still, it is still a problem?

I can increase, a little bit, the parameter that defines if the small movement of the finger should be ignored or not. Higher value anyway should mean that this tool appears on the map in cases, user does not want. Anyway, small increase should not be a big problem, so in the next version (3.33.2.3+), it should be little better.

photo
1

Hi Menion,

I'm not able to measure with my two phones or my tablet when these devices lie on the table ;) Sometimes it happens accidentally. Maybe it has to do with the screen protectors... but touch is working without any problem.

Thanks for increasement :D

Wolfgang

photo
1

Hi Menion,

I'm still to "stupid" to get it working. (v3.34.1) Sometimes it works when I don't want to...

But now I did a test. I reset (on my testing device) locus then it worked like a charm. Then I restored the settings with a backup of my normal device and now it works sometimes on the testing device.

Currently I'm a bit afraid of to the a backup and restore of my normal device. Maybe there is some time next weekend for that.

Regards Wolfgang

photo
1

Hi, so if I understand correctly, you have a "backup" that when restored on any device cause a malfunction of this feature? If so, please share it with me and I'll gladly check it. To be true, can't imagine that anything has an effect on this, but as I wrote, I'll gladly check it.

photo
1

Now on my test device (after a reboot) the measurement seems to work now. I'll do a backup/restore of my main device an week-end and let you know what happened. For the moment it does not (yet) make sense that you test it. Because maybe this backup/restore and reboot task fixed it...

photo