[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 442 in lilypond: Enhancement: RemoveEmptyStaffContext shouldn't re
From: |
codesite-noreply |
Subject: |
Issue 442 in lilypond: Enhancement: RemoveEmptyStaffContext shouldn't reduce PianoStaff to one staff |
Date: |
Tue, 01 Sep 2009 16:04:14 +0000 |
Updates:
Summary: Enhancement: RemoveEmptyStaffContext shouldn't reduce PianoStaff
to one staff
Comment #3 on issue 442 by v.villenave: Enhancement:
RemoveEmptyStaffContext shouldn't reduce PianoStaff to one staff
http://code.google.com/p/lilypond/issues/detail?id=442
I have posted a (hackish) workaround here:
http://lists.gnu.org/archive/html/lilypond-devel/2009-09/msg00005.html
Hopefully someone will come up with something better :-)
--
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 442 in lilypond: Enhancement: RemoveEmptyStaffContext shouldn't reduce PianoStaff to one staff,
codesite-noreply <=