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

[Feature Requests] libinput send events configuration #1434

Closed
pavelxdd opened this issue Jan 16, 2024 · 1 comment
Closed

[Feature Requests] libinput send events configuration #1434

pavelxdd opened this issue Jan 16, 2024 · 1 comment

Comments

@pavelxdd
Copy link

Hello. I'm currently looking into Sway alternatives, and find that all other WMs out there do not support the libinput Send Events Mode setting.

It allows to automatically disable the touchpad when external mouse is connected, and enable it again when mouse is disconnected. I find it very useful, instead of manually disabling and enabling touchpad via hotkeys.

The example of this setting configuration in Sway:
https://github.com/swaywm/sway/blob/master/sway/input/libinput.c#L222
https://github.com/swaywm/sway/blob/master/sway/input/libinput.c#L19

From sway-input man:

input <identifier> events enabled|disabled|disabled_on_external_mouse|toggle [<toggle-modes>]

Enables or disables send_events for specified input device.
Disabling send_events disables the input device.
The toggle option cannot be used in the config.
If no toggle modes are listed, all supported modes for the device will be toggled through in the order: 
enabled, disabled_on_external_mouse, disabled, (loop back). 
If toggle modes are listed, they will be cycled through, 
defaulting to the first mode listed if the current mode is not in the list. 
They will also not be checked to see if they are supported for the device and may fail.

Is it possible to support this libinput setting in labwc?

@ludg1e
Copy link
Contributor

ludg1e commented Jan 16, 2024

Just adding that this is a duplicate of #559 and there's the draft PR #961

@ahesford ahesford closed this as not planned Won't fix, can't repro, duplicate, stale Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants