Re: [Lilypond-auto] Issue 4151 in lilypond: implicitTimeSignatureVisibility

[lilypond]

Comment #1 on issue 4151 by tdanielsmusic: implicitTimeSignatureVisibility
https://code.google.com/p/lilypond/issues/detail?id=4151

The implicitTimeSignatureVisibility property was implemented in Jan 2007  
with committish ba55916d8aca7be7fc056630e55548a8f5cf38d7.  The commit  
comment says, "New time signature on starting staff in next system doesn't  
take space."  The property is implicit because it sets the break-visibility  
property implicitly.  Maybe the word "default" was used because it was  
correcting a fault whereby the default 4/4 was shown at the end of the  
system and the beginning of the next system, since the default initial  
value for the TimeSignature grob is all-visible, but that's just  
surmising.  Maybe more recent changes elsewhere have affected the semantics.

Whatever the history, its current utility seems to be, as Dan pointed out,  
to control the visibility of the very first time signature.  I don't think  
there is any other way of doing this (?)  So I agree, a doc change seems to  
be required here.  And maybe a change of name to  
initialTimeSignatureVisibility.


--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings