On 27/12/2012 13:38, Tobias Bieniek wrote: > I see. Maybe a "screen lock" might be more suitable though? Have you > thought about that idea in contrast to your suggestion? I know that > the PG pilots have expressed their need for a screen lock too once or > twice.
I think the objective is to have XCsoar respond to deliberate input and not inadvertent input. In my case the inadvertent inputs are mainly "tap map" inputs. Other occasional inadvertent inputs are from touching the Android soft buttons. (I don't think there is much that can be done about the soft keys and they are, literally, a much smaller problem.) The Android "long touch" is available on the platform, it is not being used for anything else at the moment and (like gestures) is highly unlikely to be input inadvertently. The "tap map" function is only required occasionally, hence my suggestion to use a long touch to access this feature. A lock screen function would require an additional action to unlock it before any other input could be made. After unlocking the screen you can still activate "tap map" by mistake while entering gestures etc. This might work for paragliding pilots but for me it would be a bit of an overkill. Thanks Ian ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_122712 _______________________________________________ Xcsoar-user mailing list Xcsoar-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcsoar-user
