Re: help with frameEngraver-bars-and-boxes function

[David Nalesnik]

On Mon, Jan 9, 2017 at 8:32 AM, address@hidden
<address@hidden> wrote:
>
> On Jan 8, 2017, at 5:39 PM, James.Correa <address@hidden>
> wrote:
>
> Hi,
>
> This is my first time writing on the list. I have using lilypond for a few
> months, and I find in the list archive a function written by David Nalesnik
> that is exactly what I need for my score. It compiles ok on Lilypond 2.18.2,
> but I am using 2.19.53 for my score and I am getting this warnings:
> Starting lilypond 2.19.53 [frameEngraver-boxes-and-repeats-example.ly]...
> Processing
> `/Users/jamescorrea/Downloads/frameEngraver-boxes-and-repeats-example.ly'
> Parsing...
> warning: type check for `FrameStub' failed; value `#<Grob_properties>' must
> be of type `list'
> warning: type check for `FrameBracket' failed; value `#<Grob_properties>'
> must be of type `list'
> warning: type check for `FrameExtender' failed; value `#<Grob_properties>'
> must be of type `list'
> warning: type check for `Frame' failed; value `#<Grob_properties>' must be
> of type `list'
> Interpreting music...
> Exited with exit status 1.
>
> My code skills aren't enough to fix it. Can someone help me?
> I am attaching the .ily file, I hope the author will be ok with.
> Thanks in advance!!!
>
>
> Hi James,
> Here’s a tidbit I filed away the last time frameEngraver was discussed:
> "
> ...should mention that this needs 2.18.x  There is a single change which you
> need for current development versions.  See the last line below:
>
> %%%%%%%%%%%%%%%%%%%%%%%%% ADD NEW GROB DEFINITIONS
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>
> #(define (add-grob-definition grob-name grob-entry)
>    (let* ((meta-entry   (assoc-get 'meta grob-entry))
>           (class        (assoc-get 'class meta-entry))
>           (ifaces-entry (assoc-get 'interfaces meta-entry)))
>      (set-object-property! grob-name 'translation-type? ly:grob-properties?)
> ;; NB!!
> “
>
> I think this was Nalesnik speaking. I don’t know enough to say that this
> will fix the problem, but I hope it helps. I've used frameEngraver
> extensively, so I want to see it continue to function!
> Best,
> Holland
>

Yes, me speaking :)  This should fix the problem.

David