Hi David,
>> Unless Forbid_line_break_engraver has been removed.
> Yes, that’s one of the reasons I used the quotes around "must"… =)
To that point:
My solution was… unconventional, shall we say… But it solves the problem in
what I estimate would be >99% of the scores that Lilypond users would
Hi David,
>> Working with Andrew’s "spacer" situation, I see now that my staff
>> layout functions can be simplified significantly: since every break
>> "must" be accompanied by a bar (even if it’s an invisible one!),
>
> Unless Forbid_line_break_engraver has been removed.
Yes, that’s one of the
Hi Kieren,
> In the snippet below, you can see the effects of forcing visibility
> (\showStaff), forcing invisibility (\hideStaff), and reverting to normal
> (\resetStaff). Note that these functions can also be used with \once, if
> desired (though I haven’t in this snippet).
[snip]
> %%% SNIP
Kieren MacMillan writes:
> Hi all,
>
> Working with Andrew’s "spacer" situation, I see now that my staff
> layout functions can be simplified significantly: since every break
> "must" be accompanied by a bar (even if it’s an invisible one!),
Unless Forbid_line_break_engraver has been removed.
>
Hi all,
Working with Andrew’s "spacer" situation, I see now that my staff layout
functions can be simplified significantly: since every break "must" be
accompanied by a bar (even if it’s an invisible one!), one can simply use that
interface (and no others!) to force visibility.
In the snippet
Hi Valentin,
> Huh.
> http://lilypond.org/doc/latest/Documentation/internals/skip_002devent
> "Not accepted by any engraver or performer. "
That is a little unfortunate…
> How about putting ordinary rests and removing the stencil?
> (I know, it’s ugly, but…)
See the "bar-line-interface" solutio
Hi Reggie (and Andrew et al.),
> Can you share your function code with us please?
Andrew’s snippet is included, below, with my functions applied.
Andrew: I believe my addition of "bar-line-interface" to \showStaff solves your
[more specific] issue, except in the very rare (?!) case that you hav
Kieren MacMillan wrote
> Hi Reggie,
>
>> Why has nobody offered this "solution" if it's common knowledge
>> to all who know the manual line by line?
>
> The solution — including essentially my \showStaff and \hideStaff
> functions, under different names — has already been posted in this very
> th
Kieren MacMillan wrote
> Reggie,
>
>>> You don’t have to; I select staves and have them appear
>>> and disappear as desired all the time.
>>
>> * Then why can't Andrew? Why did he post in the first place?
>> Why is a hack the only answer solution?
>
> In an application where you type r8 when you
Hi Reggie,
> Why has nobody offered this "solution" if it's common knowledge
> to all who know the manual line by line?
The solution — including essentially my \showStaff and \hideStaff functions,
under different names — has already been posted in this very thread (by
Jean-Charles).
Please go
Reggie,
>> You don’t have to; I select staves and have them appear
>> and disappear as desired all the time.
>
> * Then why can't Andrew? Why did he post in the first place?
> Why is a hack the only answer solution?
In an application where you type r8 when you want to output the visual
represen
David Kastrup wrote
> Please work on your quoting. It's rather hard to figure out who said
> what.
>
> Reggie <
> reegistoop@
> > writes:
>>
>>> Lilypond is so bizarre sometimes with things.
>>
>> A totally useless and inflammatory comment.
>>
>> * Respect, but there are many things in Lilypond
Please work on your quoting. It's rather hard to figure out who said
what.
Reggie writes:
>
>> Lilypond is so bizarre sometimes with things.
>
> A totally useless and inflammatory comment.
>
> * Respect, but there are many things in Lilypond code that is bizarre
> and confusing. Even those who
Hi Reggie,
> I would also want to know how to do this basic layout setting which all
> other notation Programs have done since the dawning of time.
That claim seems hyperbolic, and almost certainly not true. (If I recall
correctly, NoteWriter v1 didn’t have any such ability.) In any case, saying
Hi Reggie,
> I would also want to know how to do this basic layout setting which all
> other notation Programs have done since the dawning of time.
That claim seems hyperbolic, and almost certainly not true. (If I recall
correctly, NoteWriter v1 didn’t have any such ability.) In any case, saying
Andrew Bernard wrote
> I want to remove some staves containing only rests and yet retain others
> in
> my quartet score. [When there is a long solo I want the other parts
> suppressed, but when just one instrument is at rest I want the empty staff
> to show in the set of four].
>
> The keepAliveIn
On 2/4/19, Andrew Bernard wrote:
> OK. But am I on the right track in general? Seems very complex for a
> conceptually simple thing to want to do, so I am concerned I am way out
> here.
A more basic solution would be to add an invisible voice in these specific bars:
<< s1*4 \\ hide c >>
But no
Le 04/02/2019 à 10:17, Andrew Bernard a écrit :
I want to remove some staves containing only rests and yet retain others in
my quartet score. [When there is a long solo I want the other parts
suppressed, but when just one instrument is at rest I want the empty staff
to show in the set of four].
HI Valentin,
OK. But am I on the right track in general? Seems very complex for a
conceptually simple thing to want to do, so I am concerned I am way out
here.
Andrew
On Mon, 4 Feb 2019 at 22:15, Valentin Villenave
wrote:
> On 2/4/19, Andrew Bernard wrote:
> > So now I can selectively show a
On 2/4/19, Andrew Bernard wrote:
> So now I can selectively show a stave containing only rests, but what about
> one containing only spacers? I am unable to find what interface that is.
Huh.
http://lilypond.org/doc/latest/Documentation/internals/skip_002devent
"Not accepted by any engraver or per
Partially answering my own question, I now see that the \unset idea does
not work, and you have to reset the keep alive interfaces list to the
initial list. [I got the unset idea from some archive posts.]
So now I can selectively show a stave containing only rests, but what about
one containing on
I want to remove some staves containing only rests and yet retain others in
my quartet score. [When there is a long solo I want the other parts
suppressed, but when just one instrument is at rest I want the empty staff
to show in the set of four].
The keepAliveInterface must have something to do w
22 matches
Mail list logo