Comment #35 on issue 4022 by [email protected]: Patch: Allow specifying
different alignment for grob and its parent
http://code.google.com/p/lilypond/issues/detail?id=4022
@regtest results (comment #32):
<facepalm>. What a complete fail of mine... I'll set parent-alignment-*
of affected grobs to whatever is needed to get correct behavior and
re-upload. (The logic of the code was ok, it's just missing properties.)
@David:
I can change it like this. As for what is nicer and easier to understand,
i'm not really sure... One thing that can be hard for users in your
proposal is the different meaning of #f and '() - i'm pretty sure that
beginner users may confuse them (i think that for quite some time i was
thinking of both of them as "a gizmo that means 'unset'"). Apart from that
it's fine.
Oh, btw - do i understand correctly that there is no such thing as
a "default value for a property in general"? I mean, if we have a FooGrob
and some-property is not set in define-grobs.scm, FooGrob.some-property
will be '()? (Except when someone sets it in C++ code - like with
Fingering's offsets - which seems to me a very very bad thing).
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings