musescore / musescore/MuseScore

Tab selection is moved to the Beam after ticking Stemless checkbox on Stem tab (when whole measure selected)

Open
#16,955 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P2
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Other type of issue

Bug description

No response

Steps to reproduce
  1. Open the score Greensleeves_Guitar_Easy.mscz.zip
  2. Select the first measure
  3. In Properties > Note > Stem tick the Stemless checkbox

Same issue is reproducible with Feathered beams option.

  1. Open the score Greensleeves_Guitar_Easy.mscz.zip
  2. Select the first measure
  3. Go to Properties > Note > Beam
  4. Select Feathering left (Selection is moved accordingly)
  5. Select Feathering right (Selection is moved to None)
Screenshots/Screen recordings

Stemless

https://user-images.githubusercontent.com/101250347/226586506-13adc87a-53a2-462c-a765-7c4dbccfcfec.mp4

Feathering

https://user-images.githubusercontent.com/101250347/226588545-abc77805-d442-4922-82ea-0fb072a3a1d0.mp4

MuseScore Version

OS: macOS 13.2, Arch.: x86_64, MuseScore version (64-bit): 4.1.0-230760302, revision: github-musescore-musescore-5e39b1f

Regression

No.

Operating system

macOS 13

Additional context

No response

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 with Greensleeves_Guitar_Easy.mscz using a whole-measure selection, then inspect the Properties > Note > Stem and Beam controls and the selection-handling path they trigger. Done means changing Stemless or Feathering leaves the selection on the intended measure rather than moving it to the beam or another feathering state.

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.