-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
horizontal frame and system break prevent courtesy keysigs #22256
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
I'm wondering what the best way to solve this would be... A toggle in properties for horizontal frames "Display courtesy keysig, timesig, clef in previous measure" ? |
I don't think that's needed, it should just work, unconditionally, just as if those frames weren't there. |
Even when the new measure is on the same system? Because there I would argue it shouldn't be the default, but the user should still have control over whether to display it or not |
If the user wants control, (s)he should use a section break |
Ah, indeed not for horizontal frames, I had forgotten about that. They imply a system break. |
Yes, system break on a horizontal frame, which is only one of the many use cases |
But here we're dealing with horizontal frames and system breaks |
Well, yes. However since there are other instances where different behavior could be wanted, I think a more encompassing solution is best (see my example above) |
In this case, it seems like you wouldn't want the courtesy key signature, but by default it wouldn't be generated anyway? |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
I think, this is different case. I see it as a nice feature request, and original post as a bug. But if having this nice option, defaults in theese cases should be oposite. If line break, courtesy keysig should be on, if not line break, courtesy keysig should be off by default. (Of course depending on score style settings too). |
Isn't this a duplicate of #19759? |
Issue type
Engraving bug (incorrect score rendering)
Bug description
Inserting a horizontal frame
and entering a break at that frame breaks the stave all right but now there are no courtesy accidentals
Divisi arrows are beyond RH margin of bars.
Entering a break at end bar creates courtesy accidentals, as expected.
Suppose we want the divisi arrows to end at the same right hand margin as the rest of the bars?
Instead of entering a system break, inserting a horizontal frame at bar 5 and entering a break at that frame breaks the stave all right but now there are no courtesy accidentals
MuseScore Version
MuseScore version (64-bit): 4.2.1-240230937, revision: github-musescore-musescore-d757433
Regression
No
Operating system
OS: Windows 10 Version 2009 or later, Arch.: x86_64
The text was updated successfully, but these errors were encountered: