-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Percussions - Implement PercussionPanelModel and PercussionPanelToolBar #24609
Closed
mathesoncalum
wants to merge
11
commits into
musescore:master
from
mathesoncalum:percussions_frame_actions
Closed
Percussions - Implement PercussionPanelModel and PercussionPanelToolBar #24609
mathesoncalum
wants to merge
11
commits into
musescore:master
from
mathesoncalum:percussions_frame_actions
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mathesoncalum
force-pushed
the
percussions_frame_actions
branch
2 times, most recently
from
September 10, 2024 09:32
0569fb2
to
ef8ec1d
Compare
KDDockWidgets requires using two MouseAreas: one for dragging the title bar (which will drag the whole floating window when it's undocked) and one for dragging individual tabs (this will drag the tabs out of the floating window, which gives a strange effect when there is only one tab in the floating window. The design specifies that we want tabs instead of a title bar for horizontal panels even when there is only one tab. In this case, we need to make the tabs visible, but make their MouseArea disabled, and instead use the title bar MouseArea.
Old situation: you tell the docking system a navigation panel for each dock panel, and the docking system will mess with the order of this panel. Problems: if a dock panel contains multiple navigation panels, you need to chain those other panels to the first one. And if the first panel is not really available, as in the case of the mixer toolbar, you can't tell the docking system about it. New situation: you tell the docking system about the navigation section directly, instead of the navigation panel. The docking system will give you a `contentNavigationPanelOrderStart` property back, which you can use to correctly set the order of all navigation panels in your dock panel.
reset toolbarComponent when destroying panel
Turns out to be necessary after rebase
mathesoncalum
force-pushed
the
percussions_frame_actions
branch
from
September 11, 2024 11:21
ef8ec1d
to
98c8436
Compare
mathesoncalum
changed the title
Percussions - provide mechanism for adding actions to DockFrame
Percussions - Implement PercussionPanelModel and PercussionPanelToolBar
Sep 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Draft for now - still working on a couple of things.
This PR demonstrates how #22050 can be used to implement the toolbar for the percussions panel.