musescore / musescore/MuseScore
The "Minimum length" property of l.v. ties should not be limited to 10
Nobody has claimed this yet.
- 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
In style dialog, "Minimum laissez vibrer length" is settable up to 99.99sp.
But in Properties panel, "Minimum length" is limited to 10.
Based on real world example, the threshold should be relaxed to a larger value, at least to the same value as the style dialog.
Supporting files, videos and screenshots
Real world example:
In MuseScore:
What is the latest version of MuseScore Studio where this issue is present?
OS: Windows 11 Version 24H2 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.6.0-252420405, revision: github-musescore-musescore-66bd76c
Regression
No.
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
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.
Research direction
No source file or test is named. Start by locating the Properties panel control for “Minimum length” and compare its range with the style dialog’s “Minimum laissez vibrer length” control; done means the Properties panel accepts the larger range, matching the style dialog, and the relevant UI checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100