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

Chord symbol problem when fretboard diagram scale > 150% #25201

Open
4 tasks done
brettvac opened this issue Oct 17, 2024 · 0 comments
Open
4 tasks done

Chord symbol problem when fretboard diagram scale > 150% #25201

brettvac opened this issue Oct 17, 2024 · 0 comments
Labels
regression MS3 Regression from MS3 (3.6.2) UX/interaction

Comments

@brettvac
Copy link

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

Fretboard diagram scaling is problematic in Musescore 4.

In Musescore 4 Studio, create a guitar fretboard diagram on the score by dragging it from the palette.

It's easy to change the text over the fretboard diagram by double clicking the text.

However, now click on the fretboard diagram and under Scale, change the value to something like 200%.

The chord diagram will scale up but it will be impossible to click on (and edit) the text above the chord diagram.

Moreover, the text will be covered by X and O symbols above the nut, when they should clearly not cover the chord name. A workaround to this bug is to edit the style of the chord name and increase the distance to fretboard diagram. You have to edit this value before scaling due to this bug.

Supporting files, videos and screenshots

Screenshot 2024-10-17 130232

What is the latest version of MuseScore Studio where this issue is present?

OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.2-242570931, revision: github-musescore-musescore-3130f97

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

Windows 11

Additional context

No response

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
@muse-bot muse-bot added regression MS3 Regression from MS3 (3.6.2) UX/interaction labels Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
regression MS3 Regression from MS3 (3.6.2) UX/interaction
Projects
None yet
Development

No branches or pull requests

2 participants