[Ardour-Dev] Set Selected Regions

Paul Davis paul at linuxaudiosystems.com
Sun Aug 26 11:38:02 PDT 2007

On Sun, 2007-08-26 at 21:53 +0200, Esben Stien wrote:
> Chris Goddard <chris at oofus.demon.co.uk> writes:
> > Why ?
> I said why. Every operation should be atomic and undoable. Anything
> else is a bad idea, in my opinion.
> This is common in applications that deals with canvas items, f.ex
> gimp.
> Whatever you do, it's an operation and it's being appended to the undo
> list. The undo list is a feature request in ardour: 
> http://tracker.ardour.org/view.php?id=1349

its not likely ever to happen.

> I can understand that people find it irritating to go through all
> these selection operations without an undo list.
> However, removing selection operations from the list of executed
> operations instead of implementing an undo window, is a bad idea;).
> Ardour as a state machine should be aware of every operation.
> "A state stores information about the past, i.e. it reflects the input
> changes from the system start to the present moment" - wikipedia

notice the word *state*. precisely what constitutes "state" is the heart
of this argument. some people would argue that the only "state" that
matters has to do with the existence and arrangement of material along
the timeline. you apparently feel otherwise.

More information about the Ardour-Dev mailing list