Default task

[ngreenwood]

Suppose I save a task as the Default task (it might be no more than my home airfield for local soaring purposes, as suggested in the Manual).  The next time I enter a task & fly it, the progam overwrites the old task & saves the new one as the Default.  Is this really what was intended -- & if so why use the term Default?  After all, there are 10 further filenames available for other tasks I might want to save.

Would it be possible to preserve the original Default until the user explicitly overwrites it with a new one?

Nigel

[John Wharington-3]

Hi Nigel,

I'm not sure what you're asking for.

The way it works right now, "default" is used as the name because it's
the task that will be used when you start the program.  And yes it is
intended that when you save the task it becomes the default.  Also when
you exit the program, the current task is saved as the default.  It's
definitely intended that way, because the typical user will program
their task early in the day, quit the program, then when they fire it up
again prior to takeoff they want the task they just programmed to be
there.

Oh, also you have more than 10 filenames.  When you select a blank
filename, and hit save, it brings up a text editor where you can enter
any name you want.

But for your specific question about preserving the original Default,
I'm not sure what exactly you want or how the program would behave.  Can
you describe the use-case in more detail?  I'm confident that it should
be possible using a custom input events file.


Johnny


On Tue, 2008-07-15 at 04:03 -0700, ngreenwood wrote:

> Suppose I save a task as the Default task (it might be no more than my home
> airfield for local soaring purposes, as suggested in the Manual).  The next
> time I enter a task & fly it, the progam overwrites the old task & saves the
> new one as the Default.  Is this really what was intended -- & if so why use
> the term Default?  After all, there are 10 further filenames available for
> other tasks I might want to save.
>
> Would it be possible to preserve the original Default until the user
> explicitly overwrites it with a new one?
>
> Nigel
>
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Xcsoar-user mailing list
Xcsoar-user@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-user

[ngreenwood]

Hi Johnny

Thanks for the reply.

John Wharington-3 wrote:

Hi Nigel,

I'm not sure what you're asking for.

The way it works right now, "default" is used as the name because it's
the task that will be used when you start the program.  And yes it is
intended that when you save the task it becomes the default.  Also when
you exit the program, the current task is saved as the default.  It's
definitely intended that way, because the typical user will program
their task early in the day, quit the program, then when they fire it up
again prior to takeoff they want the task they just programmed to be
there.

Oh, also you have more than 10 filenames.  When you select a blank
filename, and hit save, it brings up a text editor where you can enter
any name you want.

But for your specific question about preserving the original Default,
I'm not sure what exactly you want or how the program would behave.  Can
you describe the use-case in more detail?  I'm confident that it should
be possible using a custom input events file.

I've thought a bit more about it & can now see the logic behind it.  I think it's the name "Default" that's misleading: perhaps it should be called Temp or Current. As a relatively inexperienced user, I assumed that any task saved as Default would fire up automatically each time I used the program.

It might be useful to mention in the Manual that any task saved to Default will _not_ be permanently stored (in fact it's unlikely to survive the next use of the program!).  The QuickStart/Local Flight section of the manual sort of implies that the local flight will be stored as Default until you change it.  In fact, if you want that local task stored permanently it needs to be called anything _but_ Default.

Nigel

[John Wharington-3]

Hi Nigel,

>
> I've thought a bit more about it & can now see the logic behind it.  I think
> it's the name "Default" that's misleading: perhaps it should be called Temp
> or Current. As a relatively inexperienced user, I assumed that any task
> saved as Default would fire up automatically each time I used the program.
>
> It might be useful to mention in the Manual that any task saved to Default
> will _not_ be permanently stored (in fact it's unlikely to survive the next
> use of the program!).  The QuickStart/Local Flight section of the manual
> sort of implies that the local flight will be stored as Default until you
> change it.  In fact, if you want that local task stored permanently it needs
> to be called anything _but_ Default.

Ah yes I see why the confusion now.  And you're right there that you
really don't want to call the task default if you want to save it for
much later.  The manual needs to be updated.  Hopefully I will get some
time soon to work on it.


Johnny


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Xcsoar-user mailing list
Xcsoar-user@...
https://lists.sourceforge.net/lists/listinfo/xcsoar-user