input-remapper/keymapper/dev/keycode_mapper.py

192 lines
7.0 KiB
Python
Raw Normal View History

#!/usr/bin/python3
# -*- coding: utf-8 -*-
# key-mapper - GUI for device specific keyboard mappings
# Copyright (C) 2020 sezanzeb <proxima@hip70890b.de>
#
# This file is part of key-mapper.
#
# key-mapper is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# key-mapper is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with key-mapper. If not, see <https://www.gnu.org/licenses/>.
"""Inject a keycode based on the mapping."""
import asyncio
from evdev.ecodes import EV_KEY, EV_ABS
2020-12-02 19:48:23 +00:00
from keymapper.logger import logger
from keymapper.util import sign
2020-12-02 20:20:18 +00:00
from keymapper.dev.ev_abs_mapper import JOYSTICK
# maps mouse buttons to macro instances that have been executed. They may
# still be running or already be done. Just like unreleased, this is a
# mapping of (type, code). The value is not included in the key, because
# a key release event with a value of 0 needs to be able to find the
# running macro. The downside is that a d-pad cannot execute two macros at
# once, one for each direction. Only sequentially.
2020-12-05 10:13:10 +00:00
active_macros = {}
2020-12-31 20:46:57 +00:00
# mapping of future up event (type, code) to (output code, input event)
# This is needed in order to release the correct event mapped on a
# D-Pad. Each direction on one D-Pad axis reports the same type and
# code, but different values. There cannot be both at the same time,
# as pressing one side of a D-Pad forces the other side to go up.
# "I have got this release event, what was this for?"
# It maps to (output_code, input_event) with input_event being the
# same as the key, but with the value of e.g. -1 or 1. The complete
# 3-tuple output event is used to track if a combined button press was done.
# A combination might be desired for D-Pad left, but not D-Pad right.
# (what_will_be_released, what_caused_the_key_down)
unreleased = {}
2020-12-05 10:13:10 +00:00
def should_map_event_as_btn(ev_type, code):
2020-12-02 19:48:23 +00:00
"""Does this event describe a button.
Especially important for gamepad events, some of the buttons
require special rules.
Parameters
----------
2020-12-04 16:38:04 +00:00
ev_type : int
2020-12-02 20:03:59 +00:00
one of evdev.events
code : int
linux keycode
2020-12-02 19:48:23 +00:00
"""
2020-12-12 13:12:45 +00:00
if ev_type == EV_KEY:
2020-12-02 19:48:23 +00:00
return True
if ev_type == EV_ABS:
is_mousepad = 47 <= code <= 61
if not is_mousepad and code not in JOYSTICK:
return True
2020-12-02 19:48:23 +00:00
return False
2020-12-12 13:12:45 +00:00
def is_key_down(event):
"""Is this event a key press."""
return event.value != 0
def is_key_up(event):
"""Is this event a key release."""
return event.value == 0
2020-12-31 20:46:57 +00:00
COMBINATION_INCOMPLETE = 1 # not all keys of the combination are pressed
NOT_COMBINED = 2 # this key is not part of a combination
def handle_keycode(key_to_code, macros, event, uinput):
"""Write mapped keycodes, forward unmapped ones and manage macros.
2020-12-02 16:40:21 +00:00
Parameters
----------
key_to_code : dict
mapping of (type, code, value) to linux-keycode
2020-12-31 20:46:57 +00:00
or multiple of those like ((...), (...), ...) for combinations
combinations need to be present in every possible valid ordering.
e.g. shift + alt + a and alt + shift + a
2020-12-02 16:40:21 +00:00
macros : dict
2020-12-31 20:46:57 +00:00
mapping of (type, code, value) to _Macro objects.
Combinations work similar as in key_to_code
2020-12-05 10:58:29 +00:00
event : evdev.InputEvent
2020-12-02 16:40:21 +00:00
"""
if event.type == EV_KEY and event.value == 2:
# button-hold event. Linux creates them on its own for the
# injection-fake-device if the release event won't appear,
# no need to forward or map them.
2020-12-02 19:48:23 +00:00
return
# normalize event numbers to one of -1, 0, +1. Otherwise mapping
# trigger values that are between 1 and 255 is not possible, because
# they might skip the 1 when pressed fast enough.
2020-12-31 20:46:57 +00:00
# The key used to index the mappings
key = (event.type, event.code, sign(event.value))
2020-12-31 20:46:57 +00:00
# the tuple of the actual input event. Used to forward the event if it is
# not mapped, and to index unreleased and active_macros
event_tuple = (event.type, event.code, sign(event.value))
type_code = (event.type, event.code)
# the finishing key has to be the last element in combination, all
# others can have any arbitrary order. By checking all unreleased keys,
# a + b + c takes priority over b + c, if both mappings exist.
combination = tuple([value[1] for value in unreleased.values()] + [key])
if combination in macros or combination in key_to_code:
key = combination
existing_macro = active_macros.get(type_code)
if existing_macro is not None:
if is_key_up(event) and not existing_macro.running:
# key was released, but macro already stopped
return
if is_key_up(event) and existing_macro.holding:
2020-12-12 13:12:45 +00:00
# Tell the macro for that keycode that the key is released and
# let it decide what to with that information.
existing_macro.release_key()
return
2020-12-05 10:58:29 +00:00
if is_key_down(event) and existing_macro.running:
# for key-down events and running macros, don't do anything.
# This avoids spawning a second macro while the first one is not
# finished, especially since gamepad-triggers report a ton of
# events with a positive value.
2020-12-02 16:40:21 +00:00
return
if key in macros:
macro = macros[key]
2020-12-31 20:46:57 +00:00
active_macros[type_code] = macro
macro.press_key()
logger.spam('got %s, maps to macro %s', key, macro.code)
2020-12-02 15:17:52 +00:00
asyncio.ensure_future(macro.run())
return
2020-12-31 20:46:57 +00:00
if is_key_down(event) and type_code in unreleased:
# duplicate key-down. skip this event. Avoid writing millions of
# key-down events when a continuous value is reported, for example
# for gamepad triggers
logger.spam('%s, duplicate key down', key)
return
2020-12-31 20:46:57 +00:00
if is_key_up(event) and type_code in unreleased:
target_type, target_code = unreleased[type_code][0]
target_value = 0
logger.spam('%s, releasing %s', key, target_code)
elif key in key_to_code and is_key_down(event):
target_type = EV_KEY
target_code = key_to_code[key]
2020-12-31 20:46:57 +00:00
target_value = 1
logger.spam('%s, maps to %s', key, target_code)
2020-12-02 15:17:52 +00:00
else:
2020-12-31 20:46:57 +00:00
target_type = event_tuple[0]
target_code = event_tuple[1]
target_value = event_tuple[2]
logger.spam('%s, unmapped', key)
2020-12-31 20:46:57 +00:00
if is_key_down(event):
# for a combination, the last key that was pressed is also the
# key that releases it, so type_code is used to index this.
unreleased[type_code] = ((target_type, target_code), event_tuple)
if is_key_up(event) and type_code in unreleased:
del unreleased[type_code]
uinput.write(target_type, target_code, target_value)
uinput.syn()