the idea was that snapshots would form independent versions within the--20cf3074b37e9ef5f804c246c04e
Content-Type: text/plain; charset=ISO-8859-1On Tue, Jun 12, 2012 at 9:31 AM, Leigh Dyer wrote:
> ?
* if you create a new snapshot, the current state of the session is
saved to the new snapshot, but all subsequent saves continue to go to the
"mainline"
* if you do "Save As", the current state of the session is saved to a
new snapshot, and subsequent saves will go to that snapshot (i.e. you are
now
working with the saved snapshot)
* if you load a snapshot or the "mainline", all saves will go to that
version until you do something to change that
--20cf3074b37e9ef5f804c246c04e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On Tue, Jun 12, 2012 at 9:31 AM, Leigh D=
yer <lsd@wootangent.net> wrote:
?
Hmm... not as sure as I was an hour ago ;) I thought that's how it was =
meant to work, but I haven't tested it recently. How is it supposed to =
work?
the idea was that snapshots would form independent versions within=
the session. so the following rules are supposed to apply:=A0=A0 *=
if you create a new snapshot, the current state of the session is saved to=
the new snapshot, but all subsequent saves continue to go to the "mai=
nline"
=A0=A0 * if you do "Save As", the current state of the session is=
saved to a new snapshot, and subsequent saves will go to that snapshot (i.=
e. you are now=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 working with the =
saved snapshot)=A0=A0 * if you load a snapshot or the "mainline&qu=
ot;, all saves will go to that version until you do something to change tha=
t
--20cf3074b37e9ef5f804c246c04e--
LINUX® is a registered trademark of Linus Torvalds in the USA and other countries.
Linuxaudio.org logo copyright Thorsten Wilms © 2006.
Hosting provided by the Virginia Tech Department of Music and DISIS.