musescore / musescore/MuseScore

Parts synchronization issues in tablature bends

Open
#20,508 0 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

engraving parts UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Bug description

@mike-spa @bkunda Follow up to #20504

If I move the component pieces of guitar bend arrows on tablature in a part score, some elements of the bend are not recognized as un-synchronized.

Steps to reproduce

Moving the arrow

  1. Add a full bend to some notes
  2. Move the bend arrow and see that the number and dotted line move with it
  3. See that the arrow turns orange and position is unsynced in Properties, but neither the number or dotted line become orange or unsync (they should)

Moving the number or dotted line

  1. Add a full bend to some notes
  2. Without moving the bend arrow, move the number and edit the dotted line
  3. See that neither unsync (they should)

When turning the Position syncing toggle back on for any component of the bend (arrow, number, or dotted line), all three pieces should reset

Resyncing position is not accurate

  1. Add two full bends from one dyad to another so that they vertically stack in tablature
  2. On the upper bend, move the arrow so that Position unsyncs
  3. Turn the Position toggle back on
  4. See that when syncing, the bend is positioned differently from before it was moved
Screenshots/Screen recordings

https://github.com/musescore/MuseScore/assets/20806406/1ce5b78e-d113-4d28-bf10-cc5cb19db347

MuseScore Version

MuseScore version (64-bit): 4.3.0-233491244, revision: github-musescore-musescore-87739bb

Regression

No.

Operating system

OS: macOS 14.1, Arch.: x86_64

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.