You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It would be nice to have global keyboard shortcuts to control Overlayed features like e.g.
toggling pined / unpinned mode to hide / show the channel tab header w/ buttons
opening settings window
quitting Overlayed
etc.
What do you think?
Tauri should provide most of the heavy lifting needed to support global shortcuts already, so the implementation should not be too much effort, I think.
Describe the solution you'd like
Ideally, the settings UI added a new section for the actions that can be bound, where the user can set up their bindings. This could be done via actually having a "listener" mode where the user can just press the desired shortcut. Regarding the syntax for storing the shortcuts to the config: Why not just use Tauri's format?
These shortcuts should be - obviously - global, i.e. I can press the shortcut while I'm in a game, for example.
Describe alternatives you've considered
Alternatively (and simpler to implement), we could allow inputting a string that declares the desired shortcut, e.g. something like CtrlAltShift+o).
Even simpler is to just add an entry in our config.json without any GUI to start with.
I opened a draft PR for this: #298. Bindings live in config.json in the shape you suggested above, and a new Hotkeys tab records them. It's stacked on #297 because one of the commands moves a fixed overlay to the next monitor.
Activity
Hacksore commentedon Sep 2, 2024
yeah the one challenge is we really need to get the tauri store plugin added first so we can have access to the config in rust land.
Then for the first phase of this we can allow users to set them in the config, something like how VSCode does it.
mardausdennis commentedon Oct 3, 2026
I opened a draft PR for this: #298. Bindings live in
config.jsonin the shape you suggested above, and a new Hotkeys tab records them. It's stacked on #297 because one of the commands moves a fixed overlay to the next monitor.