On Mon, 6 Nov 2006, Juergen Reuter wrote:
On Mon, 6 Nov 2006, Han-Wen Nienhuys wrote:
Without knowing the details, I think it is easiest to define a
LigatureNoteHead or XLigatureNoteHead, and a XxxxLigature in
define-grobs.scm. (X = Gregorian, Vaticana, Coherent, Mensural)
By copy
On Mon, 6 Nov 2006, Han-Wen Nienhuys wrote:
Juergen Reuter escreveu:
Ok, this may work provided that there is no code elsewhere in lily that
receives grobs, looks into them and does some things if and only if this
grob is a NoteHead. Otherwise, this code would not apply to ligature
heads, t
Juergen Reuter escreveu:
Ok, this may work provided that there is no code elsewhere in lily that
receives grobs, looks into them and does some things if and only if this
grob is a NoteHead. Otherwise, this code would not apply to ligature
heads, thus failing special treatment of note heads th
On Mon, 6 Nov 2006, Han-Wen Nienhuys wrote:
The formatting backend doesn't use subclassing at all, except for the spanner
vs. item distinction. Therefore, subclassing by definition is the wrong
approach. How to organize code should be decided by looking which code is
shared. This is easiest to
Juergen Reuter escreveu:
The easiest solution that I can see is to tolerate little polution of
"noteheads.cc" and just add the missing interface declaration at the
end of this file. However, that's not my decision...
I think that this is going about the problem in the wrong way. Given
how m
On Mon, 6 Nov 2006, Han-Wen Nienhuys wrote:
Juergen Reuter escreveu:
One theoretical solution would be to introduce a new "ligatureheads.cc"
file instead of using the "noteheads.cc" functionality. However, it turned
out that almost all of the functionality of noteheads.cc would
have to be cl
Juergen Reuter escreveu:
One theoretical solution would be to introduce a new "ligatureheads.cc"
file instead of using the "noteheads.cc" functionality. However, it
turned out that almost all of the functionality of noteheads.cc would
> have to be cloned. Even worse, some other parts of lily
On Mon, 6 Nov 2006, Han-Wen Nienhuys wrote:
Werner LEMBERG escreveu:
Consider the test file apply-output.ly. During `make web', extended
debugging is active, and processing the file gives this warning:
programming error: Grob `NoteHead' has no interface for property `text'
continuing, cro
Werner LEMBERG escreveu:
Consider the test file apply-output.ly. During `make web', extended
debugging is active, and processing the file gives this warning:
programming error: Grob `NoteHead' has no interface for property `text'
continuing, cross fingers
Hanwen, do you have an answer to
Werner LEMBERG wrote:
There are many other warnings similar to this, and I think it would be
good to fix them all.
I agree; making sure that everything in the manual works perfectly would
be a great way of finding bugs. However, I don't have the time to do
this right now, and probably not in
> > Consider the test file apply-output.ly. During `make web', extended
> > debugging is active, and processing the file gives this warning:
> >
> > programming error: Grob `NoteHead' has no interface for property `text'
> > continuing, cross fingers
Hanwen, do you have an answer to my origi
Werner LEMBERG escreveu:
Consider the test file apply-output.ly. During `make web', extended
debugging is active, and processing the file gives this warning:
programming error: Grob `NoteHead' has no interface for property `text'
continuing, cross fingers
There are many other warnings s
Consider the test file apply-output.ly. During `make web', extended
debugging is active, and processing the file gives this warning:
programming error: Grob `NoteHead' has no interface for property `text'
continuing, cross fingers
Indeed, we are changing the note heads from glyphs to text s
13 matches
Mail list logo
