osmandapp / OsmAnd

OsmAnd
https://osmand.net
Other
4.39k stars 988 forks source link

Add option for “distance by _long_ tap” #20088

Open leokennis opened 1 month ago

leokennis commented 1 month ago

Describe the idea (required)

Hi, I'm a new OsmAnd user. I like the "distance by tap" feature (https://osmand.net/docs/user/widgets/radius-ruler#distance-by-tap-tool) but once enabled, it really calculates the distance on every tap. This includes when adding points while creating a route, when clicking a POI for more info etc.

To me it would make sense to include an option to keep the normal tap as it is, and have it show the distance to a point only on a long tap / double tap / something else than a regular tap.

Tell us about the expected behaviour (required)

Old situation: with “distance by tap” enabled, every tap on screen shows the distance marker.

New situation: with “distance by tap” enabled and set to a long tap, a normal tap on screen does not show the distance marker. Only a long tap does.

Tell us about alternatives you've considered (required)

Right now the only option to avoid the behavior is to disable “distance by tap”.

Context (optional)

No response

Velomeloman commented 1 month ago

Related to https://github.com/osmandapp/OsmAnd/issues/17804#issuecomment-1665118494

Max1234-Ita commented 4 weeks ago

If I remember well, in the oldest versions of OsmAnd (talking about 1.9/2.x), it was possible to have a widget to enable or disable a "measuerement tool": it was actually very useful since I could enable it only when needed, then disable it and have OsmAnd working "as usual".

Maybe it might be re-introduced; not sure if now we can already assign that function to a custom button.

@leokennis , I think there is a workaround: (quite uncomfortable, indeed): you can create a dedicated profile with Distance by tap option pre-enabled, and switch to it when some measurement is needed, then switch back to the previous one. Not the best option, IMO... but it might work.

BobsBlueNorth commented 2 weeks ago

I second the need to refine this feature some.