We can't be sure, but we suspect that the problem is that when the user tilts the staff and inserts a glyph, Neon does the following:
Calculate the pitch of the new glyph based on where the staff used to be.
Add the glyph on the tilted staff based on the calculated pitch.
Because of this, glyphs are not added where the user clicks, but higher if the staff is tilted up, and lower if it's tilted down. We don't get staves as tilted as in my extreme example, but we do often need to increase the staff tilt enough that this issue causes problems.
@yinanazhou would it be possible to make it so that a glyph is inserted where the user clicks and then pitch is calculated from there while accounting for the staff tilt, instead of the other way around?
This one took a while to track down, but @PhoebeDM and @annamorphism figured it out! I'm just the messenger. Here is a demo:
https://github.com/DDMAL/Neon/assets/83373378/e14c584d-f590-49a5-b2d6-7834885cbf6a
We can't be sure, but we suspect that the problem is that when the user tilts the staff and inserts a glyph, Neon does the following:
Because of this, glyphs are not added where the user clicks, but higher if the staff is tilted up, and lower if it's tilted down. We don't get staves as tilted as in my extreme example, but we do often need to increase the staff tilt enough that this issue causes problems.
@yinanazhou would it be possible to make it so that a glyph is inserted where the user clicks and then pitch is calculated from there while accounting for the staff tilt, instead of the other way around?