This would make the crash at the same spot more likely (making the task
resume unusable).
On the other hand it could make automated testing of a set of igc files
easy(?) so that even alpha users would be faced with this kind of crash
really unlikely.
And maybe could bring us closer to a function "go back and forth in the
replay file", which would be awesome for testing and learning :-)
On Tue, Jul 19, 2011 at 20:17, Max Kellermann <m...@duempel.org> wrote:
> On 2011/07/18 23:53, Tibor Arpas <ti...@bidforfix.com> wrote:
> > Please let the developers know if you need this functionality. Thanks a
> lot.
>
> We could store just the trace, or recover from the partial IGC file to
> fill all the task engine internal variables (internal replay).
> That'll take some CPU power, but we could skip the expensive
> calculations, and only consider the ones that are important for
> resuming the task after the crash.
>
------------------------------------------------------------------------------
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/
_______________________________________________
Xcsoar-user mailing list
Xcsoar-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcsoar-user
