> We're going to need "performance bars" and "notation bars" in here, and a
> lot of other refinements too.
I was thinking about this because Yves has made it possible to see a repeating
string of notation drawn out in a line in performance time. This is really
useful, but the representation of bar lines does not reflect an accurate
accounting of where the bar numbers are going to fall on an actual sheet of
I started to dive into that problem, but it didn't take me long to come to a
grinding halt. This is virtually impossible to solve at a global level. I
think we're going to have to leave the existing "performance" bars alone for
the most part, and add some new layer to the notation view to calculate the
notation bar lines as perceived relative to the particular collection of
segments being viewed at the time. I don't think this can be done at a ruler
level at all.
The other sort of bar line problem is the classic example of starting before
the beginning of bar 1 and finishing out somewhere with an incomplete bar, and
then following that with the same pattern in a subsequent segment. That has
been an irritation for a long time, because it's a very common pattern in real
world music that's just a mess in Rosegarden.
Look at the attached example. In particular, note how bar 3 is completely
mangled by the notation layout code. The first note in the second segment
appears to start three beats early. The double bar line is drawn in the wrong
place. The results export to LilyPond as a mess too, with seven notes in one
D. Michael McIntyre