Re: [Audacity-devel] bug(s) 20
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Leland <le...@au...> - 2010-06-30 00:34:12
|
Vaughan Johnson wrote: > > But the interesting thing is that autoSaveMinutes is *not* on a timer. > So, as Gale pointed out, if you make an edit after autosave but before > autoSaveMinutes, then do nothing for an hour (or anything longer than > you have autoSaveMinutes set to) and Audacity is crashed, that edit is > never autosaved. That's bother me for a long while and I did look into it once. But, it fell by the wayside when I realized that there'd be threading issues if it was attempted on a timer pop. > > So here's the crazy idea: just do autosave on every PushState. Autosave > in lots of other software involves copying a ton of data, but we're just > writing an xml file (just an aup file), so it's fast. That's a really good idea. And if the time it takes is too long (maybe they're working across a network), then add additional information to the pushed state (everything needed to write the .aup) and then write it out at the next timer pop. Leland |