Re: Flag functions instead of defining glyphs directly (issue4625067)

2011-07-11 Thread lemniskata . bernoullego
This was just pushed by Mike. I close the issue. thanks, Janek http://codereview.appspot.com/4625067/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Flag functions instead of defining glyphs directly (issue4625067)

2011-07-04 Thread Carl . D . Sorensen
lgtm I can see how this will work well for defining a whole set. Carl http://codereview.appspot.com/4625067/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Flag functions instead of defining glyphs directly (issue4625067)

2011-06-30 Thread hanwenn
LGTM (I am assuming the glyphs don't change) http://codereview.appspot.com/4625067/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Flag functions instead of defining glyphs directly (issue4625067)

2011-06-25 Thread lemniskata . bernoullego
Reviewers: carl.d.sorensen_gmail.com, MikeSol, Message: This is an intermediate step that will be needed for shortened flags. Description: Flag functions instead of defining glyphs directly We will need many length variants of every flag. Therefore instead of writing flag code directly in