Re: [Rosegarden-devel] Note Editor BUG: Rests that are impossible to erase

[Chris C. <ca...@al...>]

On Wednesday 17 Dec 2003 2:36 pm, William wrote:
> Chris Cannam <ca...@al...> wrote:
> >the latter does actually always remove all rests,
> >but then does a "normalize rests" on the affected area afterwards,
> >which of course often brings them back.
>
> Why shouldn't that be considered a bug?  Does it have any kind of
> benefit?

In the notation view, not a great deal of benefit except to prevent 
you from leaving a bar with a completely bogus configuration of rests 
in it.  That can sometimes be a worthwhile feature.

In an editor such as the matrix that doesn't show rests, it's pretty 
vital to reorganise the rests as you edit because otherwise you'd 
probably get nonsense when you next opened the segment in notation.

> I'd think if the composer asks RG to remove a rest it's because
> he/she really does want that particular rest removed

Remember then that you have two separate meanings of "removing" a 
rest: either collapsing it with a neighbour, or removing it and 
leaving nothing in its place.  I contend that the former is a handy 
thing for an erase operation to do, so when do you do the latter?  
Only when the former can't work?  Then you have a very inconsistent 
interface.  Always?  Then you make it very easy to end up creating 
music that plays completely differently from how it looks on the 
score.


Chris