lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: new bar-lines / issue 1320


From: Marc Hohl
Subject: Re: new bar-lines / issue 1320
Date: Mon, 04 Jun 2012 09:39:33 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1

Am 04.06.2012 09:14, schrieb Janek Warchoł:
Hi,

On Sun, Jun 3, 2012 at 10:58 PM, Thomas Morley
<address@hidden>  wrote:
together with Marc Hohl I was working on Issue 1320 for a couple of weeks.
Now we have a first working version using a new approach to design BarLines:
wow!  Looks very impressive!

Please note, there was need to change some glyphs:
"*" - dotted-bar-line
Frankly, it always confuses me when i have to code a thick line using
"." - it's very unintuitive.  What about changing this to some other
character?  Maybe uppercase i?  It looks "thicker" - unless you use a
sans-serif font...
+1

I thought about uppercase I, too. "|I" looks not too bad.

But now we have to make a decision about further development:
We played around with the idea to replace all relevant parts of
bar-line.cc and span-bar.cc with scheme-code.
Would this be suitable?
I'm not knowledgeable enough to answer this question.

All other observations, hints and suggestions are highly apreciated!
Is this code supposed to work with 2.15.36?  I get some warnings:

warning: cannot find property type-check for `startRepeatType'
(translation-type?).  perhaps a typing error?
warning: doing assignment anyway
warning: cannot find property type-check for `endRepeatType'
(translation-type?).  perhaps a typing error?
warning: doing assignment anyway

looks like something related to http://codereview.appspot.com/6210049,
which was created after 2.15.36.
Yes, this was preliminary work for exactly this purpose, so you need
a newer version.

Regards,

Marc

cheers,
Janek

_______________________________________________
lilypond-devel mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-devel





reply via email to

[Prev in Thread] Current Thread [Next in Thread]