brisk-menu
brisk-menu copied to clipboard
[Feature Request] superkey hit to hide the menu
i'm wondering if it possible to add so when the menu is up and you press the superkey again the menu goes away? instead of pressing escape or a mouse click.
I've only been able to reproduce this issue in a VM. Are you using a VM?
No VM here, this is on real hardware a laptop with Debian 9 and Mate.
Thanks for confirming. I've found one laptop in my collection where Super
won't retract the menu.
Is this a right super key or left? And is the same super key used for closing/opening?
@ikeydoherty This is a left superkey and that is the only superkey my laptop has.
@flexiondotorg No problems :)
Greetings! I have the same problem here, an ubuntuMATE-forums member found out that it might be the Num Lock (at least in our cases) what is causing the problem. https://ubuntu-mate.community/t/brisk-menu-does-not-save-config-and-does-not-close-with-super-key/15184 cheers.
I don't like Ikey very much, so I'll leave that part to you :slight_smile:
Charming.
@ikeydoherty hahaha sorry, didn't realize it was you he was talking about.
I'm using Ubuntu MATE 18.04 and I have the same Num Lock issue: if Num Lock is on, the Left Super key only shows (opens) the menu but does not close it; if Num Lock is off, Left Super key opens and closes Brisk Menu always fine without any issue at all.
@pemartins1 - huh, thanks for that bit of info. I was finally able to reproduce this.
Bingo! When the menu is open, instead of calling the standard key-binder, we use a simple key-press-event
(since we're in a focused window, no need for a global listener) to detect Super_L
being pressed and so close the menu.
However, when NumLock is enabled, the accelerator comes back as <Mod2>Super_L
, even though the configured shortcut is just Super_L
, which means that they are not the same, and so we ignore it. The global key-binder just blacklists the <Mod2>
state (and others).
This is a simple fix. I'll work on it today and submit a pull request shortly.