lilypond-devel
[Top][All Lists]
Advanced

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

Re: lilypond ./ChangeLog input/test/to-xml.ly lily/...


From: Han-Wen Nienhuys
Subject: Re: lilypond ./ChangeLog input/test/to-xml.ly lily/...
Date: Thu, 28 Nov 2002 23:41:05 +0100

address@hidden writes:
> Ok, I am not that C++ guru.  This method should actually be something that
> in e.g. Java would be called an abstract method: Ligature_engraver just
> defines the interface of this method, but leaves the implementation to its
> subclasses (but it must be declared in Ligature_engraver itself, since it
> is virtually envoked from the process_music() code of Ligature_engraver).

ok, then


    Ligature_engraver::create_ligature_spanner () { return 0 ; }

also does the trick.

> > If the engraver doesn't create anything (which is not the case, it
> > seems), then the /*creats */ entry should simply be empty.
> 
> Most probably.  But if I recall correctly, there was some problem with
> acknowledge_grob() not being called in some cases.  Hence, when putting
> the creats entry empty, one should double check that
> 
> http://lilypond.org/development/Documentation/user/out-www/lilypond/White-mensural-ligatures.html#White%20mensural%20ligatures
> 
> still shows ligatures (as the website of 1.7.8 currently does, while in
> 1.7.6, ligatures did not show).

If something like this happens, I propose that we first find out what
causes it, and only then fix it.

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




reply via email to

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