musescore / musescore/MuseScore

Ties remain visible when measure is made invisible

Open
#28,272 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
  1. With grand staff, write a measure with a tie
  2. Make the measure invisible in measure properties

The tie remains visible, other articulations are made invisible

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/5178f4f6-7a2c-4ba7-b94d-86d580798a4a

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

OS: macOS 15.5, Arch.: arm64, MuseScore Studio version (64-bit): 4.6.0-251560321, revision: github-musescore-musescore-4e613ef

Regression

No.

Operating system

MacOS15

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

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

Reproduce the issue in MuseScore Studio using a grand staff, a tied measure, and the measure visibility property. Compare the visibility handling of ties with other articulations; done means the tie is hidden along with the rest of the measure.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.