Make a long syllable that spans two staves (so the second staff starts with a toggled syllable);
Check the pitches of the neumes after the clef on the second staff--they should be correct;
Select the clef at the beginning of the second staff and insert it into the nearest syllable;
Check the pitches of the neumes again--they should now be a third too low;
Now move that same clef up or down a line--the neumes following should jump down a third;
Try to move those neumes--they will not want to.
Here's a demo, where I created a long syllable to test this. You can see that at the beginning the pitches of the orange podatus are F-A, which is correct. When I insert the clef into the toggled syllable, the neumes don't move, but the pitches become D-F (a third too low). When I move the clef, the neumes all jump down a third and can't be moved anymore.
Normally, if a clef is in the middle of a syllable it has to be inserted into that syllable, otherwise the pitches following it will be wrong. However, in this specific instance, because there's a staff break and a toggled syllable, the pitches aren't wrong, so it's not technically necessary to insert that clef into the syllable for MEI reasons. So I suppose a solution would be to prevent the user from doing so, and maybe adding a friendly message saying "Inserting that clef isn't necessary!"
It could also be friendly to let the user insert the clef into the syllable if they want to, in which case I guess the solution is fixing those little bugs.
@yinanazhou what do you think? I guess it'll depend on what the MEI likes best. I'm happy with either solution!
To reproduce:
Here's a demo, where I created a long syllable to test this. You can see that at the beginning the pitches of the orange podatus are F-A, which is correct. When I insert the clef into the toggled syllable, the neumes don't move, but the pitches become D-F (a third too low). When I move the clef, the neumes all jump down a third and can't be moved anymore.
https://github.com/user-attachments/assets/260779fa-a0bf-4d03-a415-7b4e757411b1
I can think of two solutions to this:
@yinanazhou what do you think? I guess it'll depend on what the MEI likes best. I'm happy with either solution!