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

Replacing a dynamic via palettes should not overwrite its properties #23285

Closed
avvvvve opened this issue Jun 18, 2024 · 0 comments · Fixed by #23305
Closed

Replacing a dynamic via palettes should not overwrite its properties #23285

avvvvve opened this issue Jun 18, 2024 · 0 comments · Fixed by #23305
Assignees
Labels
P2 Priority: Medium UX/interaction

Comments

@avvvvve
Copy link

avvvvve commented Jun 18, 2024

A dynamic marking can be edited by selecting it in the score, then choosing a different one in the Dynamics palette. However, doing so resets the dynamic's properties to the defaults.

Instead, the new dynamic should inherit all the properties of the dynamic it replaced.

In the video below, see that the voice of the new dynamic is determined by the choice in Preferences > Note input > Dynamics & hairpins. This should have no bearing on properties when replacing a dynamic.

dynamics_properties_replace.mp4

Note that this is already how it's working in the new dynamics popup PR: #23038

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 Priority: Medium UX/interaction
Projects
Development

Successfully merging a pull request may close this issue.

2 participants