musescore / musescore/MuseScore

Incorrect cue size interaction between lyrics and notes

Open
#23,558 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P3 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

I came across a very strange understanding of the MuseScore Studio program of what the checkbox next to cue size should affect.

  1. Enter the notes of the first voice
  2. Add lyrics to the entered notes
  3. Select the notes of the 1st voice and make them cue size.
Expected behavior

The cue size should have been both the notes and the lyrics. But surprisingly, even though when clicking on the lyrics in the properties there is a check mark opposite the cue size, the lyrics themselves are not really cue size, and the presence of a check mark means the cue size not of the lyrics themselves, but of the notes to which this lyric is added. In my opinion, this is strange and wrong.

It was expected that after the selection, the lyrics would become cue size after adding a check mark next to cue size in the properties (but this check mark was already there).

Supporting files, videos and screenshots

https://github.com/musescore/MuseScore/assets/134041121/ec6e42c6-3dc2-4307-aea3-53cf7bfb9521

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

MuseScore Studio version (64-bit): 4.3.2-241630831, revision: github-musescore-musescore-22b46f2

Regression

I was unable to check

Operating system

Windows 11

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

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.

Research direction

No source file or test is named. Start by reproducing the listed steps in MuseScore Studio 4.3.2 on Windows 11 and inspect how the cue-size property behaves for selected notes and their lyrics. Done means the behavior matches the stated expectation and the cue-size state shown for lyrics is accurate.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.