menu: If multiple menus share a keybinding, prioritize the menu on the current monitor #13079
Conversation
This file contains hidden or 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
samw-26
force-pushed
the
menu-shortcut-priority
branch
from
7341c50 to
c45dded
Compare
…ioritize the menu on the monitor with the mouse cursor.
samw-26
force-pushed
the
menu-shortcut-priority
branch
from
c45dded to
2347907
Compare
clefebvre
changed the title
Member
|
Just a heads-up, since 95e9d25, keybinding settings will complain about duplicate keybindings anywhere. You can dismiss the popup without being forced to take action. Actual behavior while using them is unchanged, but we would have to make a determination to 'ignore cases of a keybinding in multiple applet instances' or something... |
mtwebster
added a commit
that referenced
this pull request
Nov 17, 2025
same applet. This restores existing, expected behavior where multiple instances of the same applet can have the same keybinding configured. ref: #13079
Member
|
I don't really like that this only works for the menu applet. A number of default cinnamon applets support shortcuts, and there are lots of third-party spices that do also. I'd prefer to consider a solution that would address it globally.
|
mtwebster
added a commit
that referenced
this pull request
Nov 21, 2025
multi-instance xlet handling. Multi-instance applets with duplicate shortcuts (which will be their default, at least when first added), will now allow the shortcut to open the instance on the current monitor, if there is one, rather than ending up always being the most-recently-loaded instance. For example, two default menu applets, one per monitor. - By default, the super keys will open whichever instance is on the active monitor. - If you assign a shortcut to one instance that is different from the other, it will open only that instance, regardless of which monitor is active. ref: #13079
Member
|
Implemented what I talked about above in 40e360d Third-party xlets will need to make minor, simple changes to take advantage of this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
When using the menu overlay keybinding, if there are menus with the same keybinding, then it will prioritize opening the menu on the current monitor (monitor with the mouse cursor).