Skip to content
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

Allow for customization of notation elements "stacking order" in parts #26096

Open
2 tasks done
ayyydoc opened this issue Jan 14, 2025 · 2 comments
Open
2 tasks done

Allow for customization of notation elements "stacking order" in parts #26096

ayyydoc opened this issue Jan 14, 2025 · 2 comments
Labels
feature request Used to suggest improvements or new capabilities

Comments

@ayyydoc
Copy link

ayyydoc commented Jan 14, 2025

Your idea

Bring back stacking order for text styles and notation markings in parts

Problem to be solved

One of the notation conventions in the gig I'm doing encourages measuring numbers in the center of each bar. However, using MuseScore makes this quite difficult. Even if I use the offset tool for every single element in only the parts, I then have to adjust the auto-place in each part, which becomes very laborious with my time constraints.

A stacking order would allow me to keep measuring numbers at the time no matter what, notwithstanding autoplace or anything like that.

I've attached an example of what I would like MuseScore to optimize:
Screenshot 2025-01-14 at 18 09 25

Prior art

They solve it by simply making it an option to put measure numbers at the very center at the bottom edge of the instrument stave

Additional context

No response

Checklist

  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests
@muse-bot muse-bot added the feature request Used to suggest improvements or new capabilities label Jan 14, 2025
@MarcSabatella
Copy link
Contributor

Maybe I'm misunderstanding, but I'm not aware of any feature MuseScore had in the past that would have changed how this works. The "stacking order" setting of previous versions was about which elements are drawn on top of which when overlapping, not anything to do with how they are positioned or how they work with autoplace. If the goal is to change how the collisions are resolved by autoplace - which elements are moved farther away from the staff than the default - stacking order wouldn't have helped.

However, it is true that in the case of a collision between a measure number and a hairpin, MU3 would have moved the hairpin, while MU4 moves the measure number. Neither version provides control over this. But it would be useful.

@ayyydoc
Copy link
Author

ayyydoc commented Jan 15, 2025

Maybe I'm misunderstanding, but I'm not aware of any feature MuseScore had in the past that would have changed how this works. The "stacking order" setting of previous versions was about which elements are drawn on top of which when overlapping, not anything to do with how they are positioned or how they work with autoplace. If the goal is to change how the collisions are resolved by autoplace - which elements are moved farther away from the staff than the default - stacking order wouldn't have helped.

However, it is true that in the case of a collision between a measure number and a hairpin, MU3 would have moved the hairpin, while MU4 moves the measure number. Neither version provides control over this. But it would be useful.

Thank you for the clarification! I'll change the title accordingly.

@ayyydoc ayyydoc changed the title Bring back stacking order in parts Allow for customization of notation elements in parts Jan 15, 2025
@ayyydoc ayyydoc changed the title Allow for customization of notation elements in parts Allow for customization of notation elements "stacking order" in parts Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Used to suggest improvements or new capabilities
Projects
None yet
Development

No branches or pull requests

3 participants