Re: Issue 2717: Implement \single, \omit and \hide (issue 6495135)

[dak]

On 2012/09/26 09:05:18, Reinhold wrote:
> is there any particular reason why you created a new command (\single)
and
> didn't reuse \once. IMO, using \once as an indicator that the next
command
> applies only to the next item would make it more consistent.

\once does something entirely different.  It does not turn an override
into a tweak but rather marks it at being active only at the current
timestep.  \once applies at a single time, \single applies on a single
item.

My first reaction was "how can one not understand this?" but then I
reread the description, and it says
"\single can, like \once, translate larger override sets like \voiceOne
into a tweak, so you can use things like \single\voiceOne c4".

Uh, ouch.  This is a rather sense-altering distortion/contraction of
"\single, like \once, can be applied to music consisting of one or more
overrides.  It translates such an override set, for example \voiceOne,
into a tweak on the following music item, so you can use things like
\single\voiceOne c4 inside of a chord and have it only affect a single
notehead of the chord".  Which does not make all that much sense
musically since \voiceOne mostly applies to stuff like stems that are
per-chord anyway.  So I probably should rather use something like
\single\easyHeadsOn for illustration.

I'll alter the description accordingly.

http://codereview.appspot.com/6495135/