Skip to content

Conversation

XiaoMigros
Copy link
Contributor

Resolves: #29451

  • I signed the CLA
  • The title of the PR describes the problem it addresses
  • Each commit's message describes its purpose and effects, and references the issue it resolves
  • If changes are extensive, there is a sequence of easily reviewable commits
  • The code in the PR follows the coding rules
  • There are no unnecessary changes
  • The code compiles and runs on my machine, preferably after each commit individually
  • I created a unit test or vtest to verify the changes I made (if applicable)

@its-not-nice
Copy link
Contributor

Thanks! This works well for unbeamed notes and is a welcome improvement:

image

Less good in cross-staff situations where they often need to be moved outside the beam. Compare the marcatos, which are behaving themselves:

image

In any case, a vtest illustrating various situations would be very welcome here.

@XiaoMigros XiaoMigros force-pushed the fermata-crossstaff branch 4 times, most recently from 1b025d0 to 91062e4 Compare August 29, 2025 15:01
@XiaoMigros XiaoMigros marked this pull request as draft September 1, 2025 05:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fermata default placement doesn't understand cross-staff notation
2 participants