4 ms·
>But I think it's a bonus that applications can't listen into keys when they're not in focus. There are applications that do not run as a window, in present I
by simion314 7y ago
>But I think it's a bonus that applications can't listen into keys when they're not in focus.
There are applications that do not run as a window, in present I have a global shortcuts that run a bash or python script, I know I am a power user so I will need a way to whitelist my use case.
- PlutoIsAPlanet 7y agoThen that should be done through a mechanism provided by the desktop environment. GNOME and I'm pretty sure KDE too has a method to set custom keyboard shortcuts that can execute commands.
- badsectoracula 7y ago> GNOME and I'm pretty sure KDE too Yeah, that is the problem with Wayland: the solution to many missing features you get out of the box with X largely depends on the environment you are using.
- phs2501 7y agoI don't run a desktop environment in X. I run xmonad and terminals. I don't want a desktop environment in wayland, but it seems like that's the only way to get reasonable functionality because it can't be added piecemeal, only monolithically via the compositor.
- simion314 7y agoThis is not enough. you fix this use case but there are many others, maybe I want to make a voice/video chat app or a remote desktop app, I will need full control of the display and keyboards not some gimped implementation that is DE specific. Wayland needs to offer full access to "power users applications" if not we end up where Windows will be more friendly for the users that need this type of applications