[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: disabling point-and-click for displayed chords?
From: |
Adam Spiers |
Subject: |
Re: disabling point-and-click for displayed chords? |
Date: |
Tue, 15 Jan 2013 15:05:12 +0000 |
On Tue, Jan 15, 2013 at 9:41 AM, David Kastrup <address@hidden> wrote:
> Adam Spiers <address@hidden> writes:
>
>> Hi all,
>>
>> I need to generate point-and-click links for notes but not for
>> displayed chord names. However, \pointAndClickTypes only filters by
>> music event class, and if my understanding is correct, events in a
>> certain music class have no notion of which context they are being
>> applied in, and so this filter cannot distinguish between a note-event
>> in a Voice context and a note-event in a ChordNames context.
>
> Also, this filter is global.
Yeah, I spotted that, but I figured that even a global variable
can change state during execution so it was worth a try ...
>> Am I correct, and if so, is there any workaround? I naively tried:
>>
>> \score {
>> <<
>> \pointAndClickTypes #'()
>> \allchords
>> \pointAndClickTypes #'(note-event)
>> \new Staff {
>> \allnotes
>> }
>> >>
>> ...
>> }
>>
>> but it still created point-and-click annotations for everything.
>
> You could use an engraver in ChordNames for wiping out the (event) cause
> of the last involved grob. Then the point-and-click location would no
> longer be available...
That makes sense. Do you mean an existing engraver though, or a new
one? The only existing one which looks promising is
Output_property_engraver (which I had never heard of before). Does
that mean I do this via \applyOutput?
Thanks!