-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
Specific input device configuration #371
Comments
This should include the ability to disable the device, too |
I was looking through the current implementation and at the |
Are you referring to something in particular? For libinput settings, it should be possible to simply get the device name and find the right config section in For dynamic XKB, you need to look in |
I'm expand the request: it should be permanent/toggle (via config file) or eventually (via Use cases are: hotkeys to on/off touchpad, temporary off touchpad while mouse is connected. |
This can work similarly to |
@YaLTeR Aha, that was the "obvious" hint I was missing. My cursory look through the config and input code just missed this. Thanks! |
This is called "events <mode>" in Sway, but I choose "send-events-mode" for consistency with libinput. I think this option also applies to keyboards, but I'm not going to add the one because we don't have libinput machinery for the keyboard config, and it's unlikely that user wants to disable _all_ keyboards. OTOH, pointer devices can be disabled per type. Perhaps, this should be revisited after implementing YaLTeR#371.
This is called "events <mode>" in Sway, but I choose "send-events-mode" for consistency with libinput. I think this option also applies to keyboards, but I'm not going to add the one because we don't have libinput machinery for the keyboard config, and it's unlikely that user wants to disable _all_ keyboards. OTOH, pointer devices can be disabled per type. Perhaps, this should be revisited after implementing YaLTeR#371.
This is called "events <mode>" in Sway, but we decided to use more abstracted form for consistency with the other config items. "disabled-on-external-mouse" is added only to touchpads, but there might be other devices that support this option. I think "off" also applies to keyboards, but I'm not going to add the one because we don't have libinput machinery for the keyboard config, and it's unlikely that user wants to disable _all_ keyboards. OTOH, pointer devices can be disabled per type. Perhaps, this should be revisited after implementing YaLTeR#371.
This is called "events <mode>" in Sway, but we decided to use more abstracted form for consistency with the other config items. "disabled-on-external-mouse" is added only to touchpads, but there might be other devices that support this option. I think "off" also applies to keyboards, but I'm not going to add the one because we don't have libinput machinery for the keyboard config, and it's unlikely that user wants to disable _all_ keyboards. OTOH, pointer devices can be disabled per type. Perhaps, this should be revisited after implementing YaLTeR#371.
This is called "events <mode>" in Sway, but we decided to use more abstracted form for consistency with the other config items. "disabled-on-external-mouse" is added only to touchpads, but there might be other devices that support this option. I think "off" also applies to keyboards, but I'm not going to add the one because we don't have libinput machinery for the keyboard config, and it's unlikely that user wants to disable _all_ keyboards. OTOH, pointer devices can be disabled per type. Perhaps, this should be revisited after implementing #371.
Ability to configure specific input devices.
Syntax: something along
Resolution for a given device:
Identifier: check what other compositors use, guess it's something libinput should be exposing.
For keyboards, it should support per-keyboard XKB config.
The text was updated successfully, but these errors were encountered: