Re: tablature.ly - please test and comment

[Carl D. Sorensen]

On 5/29/09 9:20 AM, "Marc Hohl" <address@hidden> wrote:

> Carl D. Sorensen schrieb:
>> 
>> On 5/29/09 2:05 AM, "Marc Hohl" <address@hidden> wrote:
>> 
>>  
>>> Carl D. Sorensen schrieb:
>>>    
>>>> [...]
>>>>      
>>> There is some drawback/difference: the crosses are drawn without
>>> whiteout, so they look different. Is there a way to change this?
>>>    
>> 
>> Yes.  Change the stencil so that it is a composite stencil.
>>  
> But how can I find out whether the tweak is called within a normal or a
> tab staff? Within a normal staff, a whiteout should surely be avoided ...

I think you have to do this within the callback, where the context is
available.  Once you have a context, you can see if it's a Voice context or
a TabVoice context.  I'm sure Neil can help with this better than I can.
But if you do a git grep for context, you'll see lots of examples of how to
get information about contexts....

>>  
>>>> 
>>>> Marc, feel free to add this to tablature.ly if you want to.
>>>> 
>>>>      
>>> How should we call this? It should be clear that
>>> \deadNotes works as expected, and the new function is meant
>>> to be used inside chord constructs  only.
>>> \chordNoteDeadNote sounds a bit strange ...
>>>    
>> 
>> I would recommend \deadNote, since it only applies to the next note.
>>  
>>> The matching case for \palmMute, namely
>>> \chordNotePalmMute seems to be ok for me.
>>> 
>>>    
>> 
>> I haven't reviewed the code carefully, but I think that \palmMute should
>> apply only to the next note, and \palmMuteOn should change all notes to palm
>> mute notes, or \palmMuteNotes could apply to a whole music expression.
>>  
> Yes, that's how it works now (you can use \palmMute { ... } to treat
> several notes at once, or \palmMuteOn ... \palmMuteOff).
>> 
>>  
>>> Or just simply use \chordDeadNote /  \chordPalmMute ?
>>>    
>> 
>> I don't like the \chord* notation because they aren't limited to use in
>> chords.  They will work for any single note, won't they?
>>  
> No, the tweaks will work only in chord constructs
> as far as I know, so I should have a pair of functions
> for each feature, i.e.
> 
> c4 d \palmMute e f
> 
> < c \chordPalmMute e g >4
> 
> c4 d \deadNotes e f
> 
> < c \chordDeadNotes e g >4
> 

Oh, I wasn't expecting that the new function wouldn't work outside of chord
constructs.

How about using the same function both inside and outside of the chord
constructs, and just including a check to see if the argument is a
NoteEvent.  If it is, use the \tweak method, and if it's not, use the
existing method?

I haven't tried this out, but I think it could be made to work, and if it
could, then it would greatly simplify things for the users.

HTH,

Carl