Going back to replacing the clef only. Old glyph is no longer in the
patch, we may discuss it separately.
http://codereview.appspot.com/4664070/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-dev
I guess this fixes the problem with "old" style for non-G clefs.
http://codereview.appspot.com/4664070/diff/8001/lily/clef.cc
File lily/clef.cc (right):
http://codereview.appspot.com/4664070/diff/8001/lily/clef.cc#newcode51
lily/clef.cc:51: str = str + "_" + clef_style;
On 2011/07/17 21:09:45,
2011/7/16 Janek Warchoł :
>> This is exactly the thin edge of the \override glyph
>> wedge I was worried about earlier :( We already have
>> too many overrides.
>
> I think we shouldn't delete it immediately. We sometimes leave old
> syntax for some time; let's keep old clef glyph until 2.18. T
http://codereview.appspot.com/4664070/diff/8001/lily/clef.cc
File lily/clef.cc (right):
http://codereview.appspot.com/4664070/diff/8001/lily/clef.cc#newcode51
lily/clef.cc:51: str = str + "_" + clef_style;
you can't add clef_style unless you know glyph == "clefs.G"
http://codereview.appspot.com
2011/7/16 Trevor Daniels :
>
>> \override Staff.Clef #'style = #'old tells Lily to use previous clef
>> glyph instead of my new clef.
>> (dedicated to James)
>
> This is exactly the thin edge of the \override glyph
> wedge I was worried about earlier :( We already have
> too many overrides.
I th
\override Staff.Clef #'style = #'old tells Lily to use previous
clef
glyph instead of my new clef.
(dedicated to James)
This is exactly the thin edge of the \override glyph
wedge I was worried about earlier :( We already have
too many overrides. If the majority want to change
the clef let'
New patch set uploaded.
\override Staff.Clef #'style = #'old tells Lily to use previous clef
glyph instead of my new clef.
(dedicated to James)
http://codereview.appspot.com/4664070/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://list
New patch set uploaded - the suggested clef is a bit higher now. Images
can be found in tracker issue:
http://code.google.com/p/lilypond/issues/detail?id=1752
http://codereview.appspot.com/4664070/
___
lilypond-devel mailing list
lilypond-devel@gnu.or
2011/7/9 :
> Please add an issue to the tracker, with images of both clefs, so we can
> see the comparison side by side. There should be pdf versions of both
> clefs, or high-resolution images (1200 dpi or so).
http://code.google.com/p/lilypond/issues/detail?id=1752
i'll add some pdfs tomorrow,
Please add an issue to the tracker, with images of both clefs, so we can
see the comparison side by side. There should be pdf versions of both
clefs, or high-resolution images (1200 dpi or so).
Thanks,
Carl
http://codereview.appspot.com/4664070/
__
Reviewers: Reinhold, james.lowe_datacore.com, x.scheuer_gmail.com,
Message:
A tip to speed up work if you try to modify clef shape: use this script
to generate a dvi preview of glyphs (no need to run make, and it also
shows metafont control points):
#!/bin/bash
mf '\mode:=proof; input feta20'
gf
11 matches
Mail list logo