Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Register shortcuts under wayland #282

Open
stefonarch opened this issue Mar 20, 2024 · 5 comments
Open

Register shortcuts under wayland #282

stefonarch opened this issue Mar 20, 2024 · 5 comments
Labels

Comments

@stefonarch
Copy link
Member

stefonarch commented Mar 20, 2024

Expected Behavior

We can use lxqt-globalkeysd under wayland

Possible Solution

Also for other global shortcut systems to work with KWin it’s needed to port them to use KGlobalAccel internally when running in a Plasma/Wayland session (that’s also a good idea for X11 sessions as KGlobalAccel can provide additional features like checking whether the key is already taken by another process).

  • Wrapper for writing to different compositors configs (workaround)
@tsujan
Copy link
Member

tsujan commented Mar 20, 2024

lxqt-globalkeys heavily depends on X11. A totally different code might be needed.

As you already know better than I do, Wayland WMs (and especially, labwc) come with their own shortcut handling because, unlike the case of X11, they can't be just WMs.

@redtide
Copy link

redtide commented Apr 23, 2024

Use backends there too? Basically lxqt global keys becomes a gui frontend like an ObKeys on labwc etc, moving the current code to a x11 backend.

@marcusbritanicus
Copy link

@redtide while this is a reasonable suggestion, there isn't a common protocol which can be used for a generic backend. Do you know of any wm that allows registration of arbitrary key-bindings? We may have that support in Wayfire using its IPC mechanism. But that's still under development, and isn't released yet, I think.

@redtide
Copy link

redtide commented Apr 23, 2024

ATM only OB and Labwc but it doesn't matter, what I'm saying is to make GlobalKeys like a wrapper/frontend that can adapts to various implementations. One could be also the portal mentioned in the OP.

@marcusbritanicus
Copy link

The thing with the portal is that it still requires support from the compositor. The portal will contain the code that will communicate with the compositor. Currently, we do not have any means of communication - typically, this is via a protocol (wayland/wlroots/private) or some IPC mechanism.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants