I am having the same issue when interacting with XCSoar, such as when trying to
zoom and change pages. I often get the map list instead, which then require
additional tap to cancel.
I agree with Kevin that it will be better to show the map list only when
tapping a waypoint or an airspace. I understand that the tradeoff will be not
being able to check distance and arrival altitude to places which are not in
the waypoint list.
Other than that the map elements is a great feature when clicking on an area
with multiple waypoints and/or airspace, allowing you to select the info you
want. I just wish it would cover a little larger area, as it often takes
multiple attempts to bring up a waypoint even when tapping carefully.
Ramy
>________________________________
> From: Kevin Ford <f...@math.uiuc.edu>
>To: XCSoar Users List <xcsoar-user@lists.sourceforge.net>
>Sent: Thursday, May 17, 2012 6:47 AM
>Subject: [Xcsoar-user] double-click interval too short
>
>
>I opened a ticket on this issue. The double-click interval is very short,
>about 1/4 second in ver 6.3.1. In flight trying to double-tap with a
>finger most often produces "Map element at this location" instead of
>bringing up the main menu. This is incredibly annoying, as I had to hit
>"Cancel" to get back to the map over and over again. Missing the
>double-click interval in 6.2.6 simply did nothing and left me on the map
>page, and the double-click interval was longer (at least 1/3 second on the
>linux version). In flight, since "Map element..." is a single-click mode,
>I thought that I wasn't tapping hard enough to register the double-tap.
>Harder and harder I tapped and still the same error :-( Only
>experimenting with the linux version (with a mouse) did I find the actual
>problem.
>Further experimenting on the ground with my PNA revealed that light taps
>do not often register, and double-hard taps take longer. I suggest
>increasing the double-click interval to 1/2 second or more, now that
>single-clicking on blank part of the map has another function in 6.3+.
>Better yet, in addition remove the "single-click gives "Map element..."
>page" entirely. If I click on an airport, OK, but a single click on a
>blank part of the map should not do anything (in turbulence it's easy to
>accidently touch the screen if your hand is near).
>
>Kevin Ford
>
>
>------------------------------------------------------------------------------
>Live Security Virtual Conference
>Exclusive live event will cover all the ways today's security and
>threat landscape has changed and how IT managers can respond. Discussions
>will include endpoint security, mobile security and the latest in malware
>threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>_______________________________________________
>Xcsoar-user mailing list
>Xcsoar-user@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/xcsoar-user
>
>
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Xcsoar-user mailing list
Xcsoar-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcsoar-user
