I haven't played with v9 in flight much yet, and normally, in flight, all I ever do is watch iFly instead of interact with it. (No Internet or ADS connectivity in flight.) So all I ever do is scroll the map around and/or zoom in/out in non-demanding VFR situations. (It would be different if I flew IFR.)
Still, I image it must be difficult, from the designer's perspective, to design a multifaceted app that essentially has only a left mouse click as its only input. So that got me thinking.
Actually, we have more than a single input to differentiate from. We have Multi-touch.
For example, two fingers pulls up the ruler. It pans too, but if we constrained three fingers only to pan, then there could never be any confusion as to what the app should do with two touches, be they a tap or long touch.
While admittedly not 100% intuitive, three fingers on the chart solely for panning would leave Brian more "head room" to reduce false positives on single taps. That is, if the app knows that a long single touch can only mean "rubber band" (instead of "pan the chart"), then there's less chance for confusion in the cockpit. Especially in turbulence, where you might want to rubber band your way around a TRW instead of pan.
So how about a user option to constrain iFly to three touches for panning to see if it catches on? Think of it as a "usability study."
(As it is now, iFly is confused by panning around with three touches. For some reason, it vacillates between panning and zooming.)
Four touches could be reserved for an Emergency screen, since I doubt that anyone intentionally ever uses 4 fingers (or 3 and their thumb) on the screen.
|
|