New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BOL Shifts interact with invisible clefs #683
Comments
It sounds like the less easy way is the way to go. |
I've run into a problem with fixing this. It appears that when there is no clef the first line of the score starts immediately while there is a small fixed space before the first element of the subsequent lines. You can see this in the new test I added on rpspringuel/gregoiro-test@e170fd9. I don't have time at the moment to track this bug down. Hopefully I should get to it tomorrow, but I may not have the time. Should the tracking this down be complicated, or I simply don't have enough time to get to it soon, do we want to postpone the pushing 4.0 out the door until it gets fixed, or should we simply push fixing the bug off. As far as I can tell, this is the last outstanding issue which remains on 4.0. If we push this off, we could release 4.0 tomorrow. |
I could go either way with this. I don't think this is used enough that it will bother a lot of people as long as it's fixed soon after, in 4.0.1. |
I Agree with @henryso, 4.0.1 can be released soon after 4.0.0, this bug is small enough to be in the |
I can add a section like that when prepping the 4.0 release. Which I'll do on Tuesday (Immaculate Conception is the Patronal Feast of CUA, so no classes), unless there are objections. |
I noticed this as I was preparing the revised summary, but when the automatic clefs are set to be invisible, the bolshift causes the text to stick out into the margin. This should not happen. There are two ways to implement this:
\gresetclef{invisible}
is called, it automatically calls\gresetbolshifts{disabled}
. The problem is that what to do when\gresetclef{visible}
is called later.The text was updated successfully, but these errors were encountered: