lilypond-user
[Top][All Lists]
Advanced

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

Re: forcing a specific notehead glyph


From: Phil Holmes
Subject: Re: forcing a specific notehead glyph
Date: Mon, 1 Apr 2013 13:15:29 +0100

It's not obvious, but this page should help:
 
http://lilypond.org/doc/v2.17/Documentation/contributor/compiling-regression-tests

--
Phil Holmes
 
 
----- Original Message -----
Sent: Monday, April 01, 2013 1:01 PM
Subject: Re: forcing a specific notehead glyph



2013/3/31 Neil Puttock <address@hidden>
On 31 March 2013 12:05, Thomas Morley <address@hidden> wrote:

> Hi,
>
> I downloaded 2.17.15 this morning and tried to compile my code, again: no
> problem.
> Perhaps some copy/paste error?
> To be sure, I've attached the file.

Your code does naughty things inside a callback.

I should have seen the problem myself :( 

 LilyPond turns a
blind eye to such things unless you're compiling with optimising
disabled.

I don't know anything about optimising.
Searching the archives, it seems that optimising is enabled in every released version.
IIUC, it could be disabled for compiling LilyPond from master.
How to do, i.e what should I type?
I found no hint in our manuals.

alwaysPrintWholeLaThinBassDrum =
\override NoteHead #'duration-log =
  #(lambda (grob)
     (let* ((style (ly:grob-property grob 'style))
            (grob-probs (ly:grob-properties grob))
            (cause (assoc-get 'cause grob-probs))
            (drum-type (ly:prob-property cause 'drum-type)))

     ;; If laThin-NoteHead for bassdrum is detected,
     ;; change duration-log, else default.
     (if (and (eq? style 'laThin) (eq? drum-type 'bassdrum))
         (ly:grob-set-property! grob 'duration-log 0)

This should just be `0'.
 
Yep.
 
Cheers,
Neil

Thanks,
  Harm


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

reply via email to

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