lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

cascading context definitions (\alias?)


From: Kieren MacMillan
Subject: cascading context definitions (\alias?)
Date: Tue, 22 Jan 2013 15:50:54 -0500

Hello all,

I'm trying to formalize my custom context collection, with the hopes of 
eventually releasing it for public use. I'm running into an issue that I'd like 
to clarify and/or fix.

I have defined several custom piano staff contexts (mostly to affect 
#'direction tweaks, but also for other things):

  \context {
    \Staff
    \name PianoSingleStaff
    \alias Staff
    \consists "Span_arpeggio_engraver"
  }
  \context {
    \PianoSingleStaff
    \name PianoSingleStaffUpper
    \alias PianoSingleStaff
    \override DynamicLineSpanner #'direction = #UP
    \override TextScript #'direction = #UP
  }
  \context {
    \PianoSingleStaff
    \name PianoSingleStaffLower
    \alias PianoSingleStaff
    \override DynamicLineSpanner #'direction = #DOWN
    \override TextScript #'direction = #DOWN
  }
  \context {
    \PianoStaff
    \accepts PianoSingleStaffUpper
    \accepts PianoSingleStaffLower
    ...
  }

I also want to have a reduction version (mostly to affect a size reduction, but 
also with other tweaks). Now I want to be able to say

    \change Staff = "context_name"

and have that work on all contexts (i.e., \PianoSingleStaffUpper, 
\PianoSingleStaffLower, \ReductionSingleStaffUpper, and 
\ReductionSingleStaffLower). Every definition I've tried has failed to allow 
this seemingly obvious "inheritance". Is there an \alias chain I can use to get 
that to work? Or should this all just wait for GLISS, at which point my work 
would be moot-ized??

Thanks,
Kieren.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]