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

Adding notes to a chord toggles articulation instead of preserving #18948

Closed
WHS241 opened this issue Aug 6, 2023 · 3 comments · Fixed by #19434
Closed

Adding notes to a chord toggles articulation instead of preserving #18948

WHS241 opened this issue Aug 6, 2023 · 3 comments · Fixed by #19434
Assignees
Labels
P1 Priority: High regression Regression on a prior release UX/interaction

Comments

@WHS241
Copy link

WHS241 commented Aug 6, 2023

Issue type

UI bug

Bug description

The UI for adding articulation during note entry is confusing; if the icon is highlighted, adding notes to a chord toggles the articulation (on-to-off as well as off-to-on) rather than enforcing the articulation mark. The toggling can become an issue if multiple articulations are chosen.

Steps to reproduce

  1. Enter note entry mode
  2. Choose an articulation (can either select from note entry bar or use keyboard shortcuts)
  3. Enter a note. As expected, the articulation is applied to the note, and the articulation remains selected in the note bar.
  4. Add a second note in the same place (can use either mouse or Shift-[note]). The articulation disappears, but the note entry bar still has the articulation highlighted.
  5. Continue adding notes. While the bar still displays the articulation as highlighted, the chord toggles between having the articulation applied and removed.
  6. Choose a second articulation while the first is currently applied, then continue adding to the chord. The chord now toggles between the two articulations, rather than apply both simultaneously.

Screenshots/Screen recordings

https://drive.google.com/file/d/1w00U_4BM-QQDk7GhJ-YvZ_79WhkiVs-1/view?usp=drive_link

MuseScore Version

4.1.1

Regression

I don't know

Operating system

Linux

Additional context

No response

@muse-bot muse-bot added the UI Visual issues affecting the UI (not notation) label Aug 6, 2023
@cbjeukendrup cbjeukendrup added UX/interaction and removed UI Visual issues affecting the UI (not notation) labels Aug 6, 2023
@oktophonie
Copy link
Contributor

See also: #18573

@zacjansheski zacjansheski added the P2 Priority: Medium label Aug 8, 2023
@zacjansheski zacjansheski added regression Regression on a prior release P1 Priority: High and removed P2 Priority: Medium labels Aug 8, 2023
@zacjansheski
Copy link
Contributor

Regression occurred between 4.0.2 and 4.1.0

@bkunda
Copy link

bkunda commented Sep 15, 2023

@mathesoncalum FYI (in case this one is up your alley!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 Priority: High regression Regression on a prior release UX/interaction
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

9 participants