Bar lines

[Han-Wen Nienhuys]

address@hidden writes:
> Because of a question in user-lilypond, I looked at the function
> scm/output-lib.scm: default-break-barline
> and noticed a few problems:
> 
> This function handles a number of bar types that are not handled
> by Bar_line::compound_barline(...), which is a problem since
> default-break-barline is only called at line breaks.
> 
> "||:" is treated twice, whereas ":||" is missing, probably an
> old copy-paste bug.
> 
> I propose to make the following change:
> 
> - Always call the function, not only at line breaks

Huh? What do you mean exactly (and what problem would it solve?) 

> - Let the function return three values "glyph in the middle
>    of the line", "glyph at line end" and "glyph at line start".

Do you mean a string (like now) or a molecule? 

> - Revise the current list of bar types. Are the "brace" and
>    "bracket" cases ever used, for example?

No. They're relics from the time before System-start-delimiters

> - Add documentation of all the bar types.

Yes, of course. It should probably be added as a Scheme docstring, and
we should figure out a way to dump doc strings for all public
functions in the internals doco.

> Suggestions, comments?

Yes, if bar-line gets a changeover, why not do dotted barlines too at
the same time, in the C++ code.


-- 

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