[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-bug
Subject:    Re: Bar lines
From:       Han-Wen Nienhuys <hanwen () cs ! uu ! nl>
Date:       2003-05-19 23:34:14
Message-ID: 16073.27126.487298.853787 () localhost ! localdomain
[Download RAW message or body]

mats.bengtsson@s3.kth.se writes:
> >>- Always call the function, not only at line breaks
> > 
> > 
> > Huh? What do you mean exactly (and what problem would it solve?) 
> 
> Sorry! The alternative would be to add the "||:", ":||", "|s" and
> more combinations that you could think of also in
> Bar_line::compund_barline(). My idea was to keep the basic ones
> in the C++ code and add the rest that only differ in how they are
> treated at line breaks in the default-break-barline function.

oh, wait: I think that you are saying that we should separate the
typography (i.e.: dots, kern, thin-line, thin-kern, thickline) from
the behavior at line breaks.

Good idea.

> > Yes, if bar-line gets a changeover, why not do dotted barlines too at
> > the same time, in the C++ code.
> 
> Of course. We already have PS code to draw the dashed lines, don't we?
> However, I'm not sure if we want a separate property dashed or if that
> aspect should be included in the string argument to \bar describing the
> bar type.

actually, like Rune suggested, putting dots in all spaces also does
the job. The dashed lines code may not be convenient, since the dashes
have to synchronized with the stafflines.

-- 

Han-Wen Nienhuys   |   hanwen@cs.uu.nl   |   http://www.cs.uu.nl/~hanwen 



[prev in list] [next in list] [prev in thread] [next in thread]