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

Active bar is moved to next row #25936

Open
4 tasks done
jtagcat opened this issue Dec 29, 2024 · 0 comments
Open
4 tasks done

Active bar is moved to next row #25936

jtagcat opened this issue Dec 29, 2024 · 0 comments

Comments

@jtagcat
Copy link

jtagcat commented Dec 29, 2024

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

  1. Work on a bar on the edge of the row/page: image
  2. Press 4, which causes the bar space to expand, and be moved to next page. image
  3. The view is correctly moved to where the selection is at (similar to text editing).

Problems:

  • When the score isn't all pauses (editing in the middle of a piece), I get very disoriented in the various black-and-white note graphics soup. Where is the bar I'm working on?
  • Undo leaves me in the new place (not back at the bottom of page 1): image
  • (Visually) referencing the previous bars is impossible.
  • On note entry with the mouse, the location of the pointer is gaslit. 2024-12-29 06-18-55.mp4 (and did you notice Mouse note entry: imaginary position shifts with bar size #25937)

Prior art

Possibly, not a one-stop solution: On closing tabs, Firefox keeps the tabs size, and reconciles after the mouse/attention is not on the tab bar. 2024-12-29 06-25-42.mp4

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

4.4.4

Regression

No.

Operating system

Arch

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants