Add non-global shortcuts #1751

Open
opened 2026-02-20 21:12:51 -05:00 by deekerman · 1 comment
Owner

Originally created by @xorbug on GitHub (Mar 20, 2020).

Hi all,
so, mumble is able to catch the PTT button even when its window is not focused. This is by design, and is exactly what everyone wants in order to communicate while doing something else (i.e. interacting with softwares running in different windows).

The downside of this behaviour is that if a very common key is bound to the PTT function, you find yourself toggling your mic on/off when it's not needed, maybe transmitting some unwanted sounds and/or causing annoyance to other mumble users. Imagine what happens when setting the PTT key to space and you go in another window to edit some text.

At the moment it seems the easy workarounds are:

  • binding a less common key combo to PTT
  • using the push to talk window (clicking with the mouse or pressing space inside it when focused)

The main obvious problem with these approaches is that the key you like the most can not be set. Setting a different one, forces you into using a less convenient shortcut. Using the PTT window also breaks the appearance (by spawning a new window) and may force the use of mouse (in order to click or just move the cursor inside it to press space).

I think some users may want to not give up on their favourite and easy keybinding for PTT, yet limiting its detection to the mumble window only in order to avoid unwanted activations.

So, considering all this, maybe an option to enable PTT only when the mumble client window is focused can be handy for some users. If it's not hard to implement it may be worth it.

Thanks to all the developers and contributors.

Originally created by @xorbug on GitHub (Mar 20, 2020). Hi all, so, _mumble_ is able to catch the PTT button even when its window is not focused. This is by design, and is exactly what everyone wants in order to communicate while doing something else (i.e. interacting with softwares running in different windows). The downside of this behaviour is that if a very common key is bound to the PTT function, you find yourself toggling your mic on/off when it's not needed, maybe transmitting some **unwanted sounds** and/or causing **annoyance** to other _mumble_ users. Imagine what happens when setting the PTT key to _space_ and you go in another window to edit some text. At the moment it seems the easy workarounds are: - binding a less common key combo to PTT - using the push to talk window (clicking with the mouse or pressing space inside it when focused) The main obvious problem with these approaches is that the key you like the most can not be set. Setting a different one, forces you into using a **less convenient shortcut**. Using the PTT window also **breaks the appearance** (by spawning a new window) and may **force the use of mouse** (in order to click or just move the cursor inside it to press _space_). I think some users may want to not give up on their favourite and easy keybinding for PTT, yet limiting its detection to the _mumble_ window only in order to avoid unwanted activations. So, considering all this, maybe an option to enable PTT only when the _mumble_ client window is focused can be handy for some users. If it's not hard to implement it may be worth it. Thanks to all the developers and contributors.
Author
Owner

@Krzmbrzl commented on GitHub (Mar 21, 2020):

I took the liberty of changing your issue's title as I think if we implement this, we shouldn't aim for providing this kind of functionality for PTT only. I think we should simply add a way to add shortcuts that are non-global, meaning that they can only be triggered if Mumble has focus.

@Krzmbrzl commented on GitHub (Mar 21, 2020): I took the liberty of changing your issue's title as I think if we implement this, we shouldn't aim for providing this kind of functionality for PTT only. I think we should simply add a way to add shortcuts that are non-global, meaning that they can only be triggered if Mumble has focus.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/mumble-mumble-voip#1751
No description provided.