On 09/16/2016 09:43 AM, Paul wrote:
% is \procE a string or a procedure? No way to tell in convert-ly
% and calling a string as if it were a procedure doesn't work
% \override NoteHead.id = #(lambda (grob `((id . ,(procE grob)
On second thought, I guess the following rewrite would w
On 09/16/2016 01:10 AM, Urs Liska wrote:
Doesn't a conversion to
#`(id . ,(existing-function))
suffice? Otherwise just follow Carl's suggestion.
Hi Urs, Almost, but you have to add a lambda wrapper to pass along the
implicit grob argument, and then there are other more challenging
complica
Am 16. September 2016 02:37:53 MESZ, schrieb Paul :
>Hi all, I'd like to improve on the "id" grob property but I wanted to
>ask about the best way to migrate users if/when we made the change I'm
>thinking of.
>
First of all, I think this is a good idea, and it comes at a good moment,
shortl
On 9/15/16 6:37 PM, "lilypond-devel on behalf of Paul"
wrote:
>
>Looking at the code, the changes seem pretty straightforward to do.
>Assuming we agree this is a good improvement to make, the question I
>have is about migrating existing user files to the new property.
>Literal strings are easy
Hi all, I'd like to improve on the "id" grob property but I wanted to
ask about the best way to migrate users if/when we made the change I'm
thinking of.
The "id" property was introduced [0] in January 2012 by commit:
ad3a9e6531e32c4403f1bdc6d203d3c94c6d411e
Adds an ID property to grobs.