At 12:57 28 October 2012, Robert Dunning wrote:
The underlying issue with appending a turnpoint to a task during flight
is
=
a US problem. This is because Americans are about the only folks who fly
M=
ATs.


Lol,

My point exactly, GN2 can't beat its simplicity...


The problem is not just the 5 or whatever clicks required to add a TP to
a
=
MAT. To help a pilot fly a MAT, the ideal glide computer should do mo
1) draw 1 mile circles around all Control points in the Turpoint file and
d=
isplay their names and numbers, making TPs highly distinguishable from
non-=
TPs and clearly visible on the map
2) when the pilot clicks one of those TPs, a "what if" screen shows the
pil=
ot information about "what if he adds the TP to the task" (estimated
finish=
time, speed, distance.) (The SN 10 reportedly shows this)
3) Then the pilot can choose to either (A) add the TP, (B) cancel and
resum=
e flying, or (C) explore other local items on the map.
The point is that the pilot's needs from the glide computer while flying
a
=
MAT are very different from his needs while flying normal XC or non-MAT
tas=
ks.

Rob Dunning

On Saturday, October 27, 2012 7:47:44 PM UTC-4, jfitch wrote:

=20
=20
Well, let me count. If it happens that I want to insert a turnpoint on
th=
e current leg, the sequence seems to be Click on TPSelect TP from
listDet=
ailsRight ArrowInsert in task. That is 5 clicks. If I want it to be
inser=
ted in the next leg, then in addition MenuTaskTurnpointsSelect TP from
l=
istUp/Down arrowCloseFly, for a total of at least 12. But perhaps
there
=
is an easier way?
=20