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

Reopen last active tab when another tab in the same panel is closed #26492

Open
4 tasks done
avvvvve opened this issue Feb 13, 2025 · 0 comments
Open
4 tasks done

Reopen last active tab when another tab in the same panel is closed #26492

avvvvve opened this issue Feb 13, 2025 · 0 comments
Assignees
Labels

Comments

@avvvvve
Copy link

avvvvve commented Feb 13, 2025

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

The new auto-open-and-close preference for the Percussion panel (introduced in this PR) make it very common for a panel to be opened and closed often.

If I have multiple tabs open in the bottom panel area (i.e. Mixer and Piano keyboard), and I open and close the Percussion panel by clicking an unpitched percussion staff and then clicking elsewhere, the bottom panel always opens the first tab in the group. Instead, it should make the last tab I had open the active tab.

This rule could apply to any group of tabbed panels, not just the bottom-docked panels.

Supporting files, videos and screenshots

When the Percussion panel gets automatically closed, 'Mixer' always becomes the active tab because it's in the first tab position. Instead, the view should return to whichever tab I had previously selected.

panel_close_remember.mov

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

Dev builds 13Feb25

Regression

No.

Operating system

macOS 15

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
Labels
Projects
Status: Some release after that
Development

No branches or pull requests

2 participants