musescore / musescore/MuseScore

Find (CTRL+F) with bar number doesn't respect bars excluded from count

Open
#23,800 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request needs design 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. Create score with anacrusis (e.g. 1/4)
  2. Verify that first bar is excluded from bar count (via bar properties)that
  3. Look on second line of score an note measure number on the left above stave
  4. Hit CTRL+F (Win) and enter the noted measure number, hit ENTER

Expected behaviour: First bar of second line is selected as this is the bar with the entered number.
Actual behaviour: Last bar of first line is selected.

Also notice that the bar/beat counter in the playback controls is not aligned with the bar count in the score.

Supporting files, videos and screenshots

Nothing to add

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

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.3.2-241630831, revision: github-musescore-musescore-22b46f2

Regression

I was unable to check

Operating system

Windows 10

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 with an anacrusis and an excluded first bar, then trace the CTRL+F measure-number navigation entry point and the playback bar/beat counter. Done means searching for a displayed measure number selects the corresponding bar and the playback counter agrees with the score's bar count.

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.