musescore / musescore/MuseScore
Element moves around erratically when using mouse to adjust position of various elements (stems/augmentation dots etc.)
Open
@mathesoncalum is already working on this.
Since Oct 4, 2024.
P2
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)
Description with steps to reproduce
- Create or open a new score with a dotted 1/4 note
- Select just the augmentation dot, enter edit mode (F2), then use the mouse to drag it around
- Expected: dot should follow mouse. Actual: dot moves around erratically.
- Exit edit mode for the dot, then select just the stem of the note (release mouse afterwards)
- Click and drag the mouse from somewhere in the middle of the stem (not where the drag handle is)
- Expected: stem should lengthen/shorten based on mouse movements. Actual: stem lengthens/shortens erratically and uncontrollably
Also after such an operation, undo appears to undo not just the position/length adjustment but creating the note in the first place.
Supporting files, videos and screenshots
https://github.com/user-attachments/assets/a486aed7-f2dc-49cb-a61b-1403a2132ceb
What is the latest version of MuseScore Studio where this issue is present?
4.3.1
Regression
I was unable to check
Operating system
Windows 11
Additional context
Possibly related to other similar issues where dragging with mouse produces unexpected results
Checklist
- This report follows the guidelines for reporting bugs and issues
- I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
- I have attached all requested files and information to this report
- I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.