[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Hiding first stem in group hides beam
From: |
Torbjörn Björkman |
Subject: |
Re: Hiding first stem in group hides beam |
Date: |
Sun, 14 Sep 2014 20:11:46 +0300 |
2014-09-14 18:53 GMT+03:00 David Kastrup <address@hidden>:
> Torbjörn Björkman <address@hidden> writes:
>
> > 2014-09-14 18:34 GMT+03:00 David Kastrup <address@hidden>:
> >> TorbjörnBjörkman <address@hidden> writes:
> >>
> >> > I try to hide the first stem in a beam group and expect this to keep
> the
> >> > beam, just as happens if you hide any other stem in the group.
> However, the
> >> > whole beam goes away.
> >> >
> >> > I run lilypond version 2.18.2 on a Mac.
> >> >
> >> > Code snippet that demonstrates the issue follows. The first two beam
> groups
> >> > show the expected behaviour and the last fails. This seems to be a
> bug.
> >> >
> >> > \score{
> >> > \new Staff
> >> > \relative c' {
> >> > \cadenzaOn
> >> > c8[ e \once \hide Stem f]
> >> > c[ \once \hide Stem e f]
> >> > \once \hide Stem c[ e f]
> >> > }
> >> > }
> >>
> >> That's the intended consequence of issue 2866
> >> <URL:https://code.google.com/p/lilypond/issues/detail?id=2866>.
> >
> > OK. Does this mean that there is currently no way of hiding the first
> stem
> > while keeping the beam?
>
> Of course not, that's just the default. If you use
>
> \new Staff \with { \override Beam.transparent = ##f } { ...
>
> then the transparency of stems will not bleed over to the beam.
>
> --
> David Kastrup
>
That worked. Thanks a heap!
The behaviour still seems to be in conflict with the principle of least
astonishment in view of the inconsistencies in my simple example, but maybe
worse astonishment arises elsewhere if things are otherwise.
Cheers,
Torbjörn
--
======================================
Torbjörn Björkman