Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
4 tasks done
obfuscoder opened this issue Jul 28, 2024 · 2 comments
Open
4 tasks done
Labels
feature request Used to suggest improvements or new capabilities needs design Design is needed UX/interaction

Comments

@obfuscoder
Copy link

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
@jeetee
Copy link
Contributor

jeetee commented Jul 28, 2024

It is by design that (currently) the find function uses the internal bar numbers when using Ctrl+F. Take into account that scores with multiple movements exist, which reset bar numbering for each movement (for example via a section break).

Having to option to find "notated" bar numbers would be a useful addition to the Find function; which would turn this into a feature request in need of design.

@bkunda bkunda added feature request Used to suggest improvements or new capabilities needs design Design is needed labels Jul 30, 2024
@wizofaus
Copy link
Contributor

Second this as a useful feature, maybe just typing "m8" to mean "go to the next measure with displayed measure number 8"? So if I have multiple parts in a score where the measure numbering is restarted, the first Ctrl+F m8 would go to the first measure numbered 8, then doing it again would jump to the next one etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Used to suggest improvements or new capabilities needs design Design is needed UX/interaction
Projects
None yet
Development

No branches or pull requests

5 participants