[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 387 in lilypond: tabstaff \set commands create a TabStaff context
From: |
codesite-noreply |
Subject: |
Issue 387 in lilypond: tabstaff \set commands create a TabStaff context |
Date: |
Wed, 04 Jul 2007 13:21:34 -0700 |
Issue 387: tabstaff \set commands create a TabStaff context
http://code.google.com/p/lilypond/issues/detail?id=387
Comment #1 by gpermus:
Mats pointed out:
> A simple workaround would be to do the property setting higher up
> in the context hierarchy, for example at the Score level, which means
> that they will be inherited to all TabStaff contexts (if there are any):
> \set Score.minimumFret = #3
Actually, I wouldn't really classify this as a bug at all. The same thing
happens in
many other situations. For example, you get an extra Staff in the following
situation:
\new StaffGroup{
\set Staff.instrumentName = "Stray stave"
<<
\new Staff{ c'' }
\new Staff { e'' }
>>
}
Issue attribute updates:
Status: Invalid
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Issue 387 in lilypond: tabstaff \set commands create a TabStaff context,
codesite-noreply <=