At least it doesn't map fully onto the way global shortcuts work in Mumble currently. If there is any interest from Mumble developers for this solution, I am willing to implement the compositor side for Weston (and all libweston-based compositors) as well as WLC-based compositors (at least via an LD_PRELOAD hack), and I may convince wlroots developers too (to be used by Sway and way-cooler, two important tiling I'm not sure it's enough in its current incarnation. (I should probably write all that to the mailing list, for the record if nothing else.) Let’s say Teamspeak is running too, pressing the key for voip/push-to-talk would lead to the action event being sent to either Mumble or Teamspeak (for example, based on the last focused one). The user could then have a Mumble-specific binding (or not), and a generic binding. For Mumble, it means you would ask for the 'mumble/push-to-talk voip/push-to-talk' action. The action are namespaced, and you are expected to use fallbacks. On the other side, compositors would have to implement the protocol and provide their user a way to link (key, mouse, touch, mind-control) bindings to said actions. To work as expected, clients (or toolkits) wanting to support global bindings would have to implement it.

I sent a proposal a few years ago and more recently, I made a cleaner one to allow for global action bindings. To have both, I went with an action-based protocol. We’re left with the fourth case (and half of the second one) that DEs had, until now, little interest in. The Media player case is mostly solved in DEs by having the compositor handling media keys and sending e.g. Also, the average user doesn’t need such tweaks in the first place. The second case would ideally be split between the first one (for launching stuff) and a non-problem, see below. Under Wayland, the first case will work as usual, since the compositor has control over the input. translating from one binding to another (like, a mouse button to a key, allowing to use mouse buttons with applications with keyboard-only bindings).xbindkeys daemon and friends, with two main usages that I know about:.There are four cases of global bindings that I am aware of: That is what you are experiencing with some clients allowing PTT to work. Since X11 clients are actually sharing one Wayland connection, through the Xwayland server, it actually means that focusing an X11 client will give input to all of them. The use can then trust their input to go where it is expected. The player above gave you the details to play around with I hope that this helps you understand it, sorry if it is stuff you already know, I wanted to show a picture but could not locate it.Not allowing clients to sniff on the input when they don’t have focus is a feature in Wayland, and it will be kept that way. I use / for my main push to talk and have # as my Logi channel whisper. The last step is to select the key used for the shortcut as in the key you press to talk only to the channel or people you want to talk to.

For example I have a specific push to talk key for the logi channel, as the FC and the rest of the fleet does not want to hear me telling someone to switch cap chain, or that my fax is almost out of triage, unless he specifically asks of course. I am guessing that you are in a fleet channel which is broken up into sub-channels, your normal push to talk will talk to everyone in the fleet channel, but your Whisper can be set to talk to only those in the channel you define. The dialogue box allows you to chose between whispering to selected users or a channel. Then under data on the same line you click in the data field and then click the button with … on it, it will open a dialogue box.

In the column Function you select Whisper/Shout. On the menu go configure, then settings, then go to Shortcuts.

Mumble push to talk key not working