-
Notifications
You must be signed in to change notification settings - Fork 9
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
[Staging] Clef misbehaviours #1248
Comments
Hi @fujinaga, @JoyfulGen, and @annamorphism , I would like to confirm with you where the default clef should be when there is no clef found. Should it be:
|
Hi @JoyfulGen, staging should be good after the changes get merged. |
I think at the meeting we agreed for option 1! @annamorphism can confirm. I do have a question though: what will happen when the missing clef is at the top of the page and there's no clef on a previous staff? Will the default clef then be top line C4? |
good catch! I think it does make sense to have the top line as the clef iff there is no "previous staff." |
Is the top line for the c-clef the most common position? |
I've found another clef misbehaviour: F clefs aren't happy. If you put an F clef on a staff without a clef or after a C clef, all the glyphs after the new F clef jump up an octave. Their pitch is then correctly calculated based on the new F clef. Demo: Neumes.after.F.clef.jumping.movYou can see that the glyphs on the staff below are also jumping, because they don't have a clef, so their default clef is the one on the previous staff. |
- When there is no previous clef found, use the default clef defined in `<staffDef>`, instead of using clef found later on the staff refs: DDMAL/Neon#1248 (comment)
- When there is no previous clef found, use the default clef defined in `<staffDef>`, instead of using clef found later on the staff refs: DDMAL/Neon#1248 (comment)
@yinanazhou I found another one: if a staff doesn't have any on it and also no clef before it, I can't move any element: I can click and drag them around, but they don't snap to a staff line or space properly. And if I undo the moving action, the previous action undoes as well, so it looks like Neon isn't registering the moving at all. Demo (I move the staff first so that you can see what the undo button does): Uploading Can't move elements without clef.mov… |
@JoyfulGen this should be fixed by now! |
@yinanazhou I can move elements on a staff without a clef now! The F clef issue is still there though, but different: now if I add an F clef to a staff, the neumes on that staff stay put, but the neumes on the staves below jump. |
Update: neumes below also jump when I moved a clef...the shape of clef doesn't really matter. |
- Fix element jump after inserting new clef - Fix element octave for elements after F clef refs: DDMAL/Neon#1248 (comment)
Hi @JoyfulGen, the elements jump on inserting clef should now be fixed on staging! (They still jump a bit on dragging now, but I will fix that in #1250 and #1252 . I think they might be caused by the same bug.) Could you please verify and close this issue if the insertion is working as expected? |
@yinanazhou it looks good! Closing issue now. |
- When there is no previous clef found, use the default clef defined in `<staffDef>`, instead of using clef found later on the staff refs: DDMAL/Neon#1248 (comment)
A pitch of a newly inserted glyph is calculated assuming top line as c4, but the glyph is placed based on the clef.
Expected behaviour:
The pitch should be calculated based on the clef.
The text was updated successfully, but these errors were encountered: