kdeconnect-kde

History

Alexander Lohnau f740a8bda8 Use target-centric CMake approach for declaring debug category This makes it easier to read, because we do not have to handle a list of files that get added to the targets. In other KDE projects, we also prefer the target centric approach. In case one wants to reuse the same category in multiple places, it would be best to create a small static lib. But for now, this is not needed.		2023-07-22 20:51:19 +00:00
..
CMakeLists.txt	Use target-centric CMake approach for declaring debug category	2023-07-22 20:51:19 +00:00
kdeconnect_remotekeyboard.json	Remove explicit plugin Id	2023-07-22 20:51:19 +00:00
README	Add remotekeyboard plugin	2017-01-23 09:08:27 +01:00
remotekeyboardplugin.cpp	Provide default implementation for KdeConnectPlugin::connected	2023-07-22 16:06:21 +02:00
remotekeyboardplugin.h	Provide default implementation for KdeConnectPlugin::connected	2023-07-22 16:06:21 +02:00

README

Sends key-events to remote devices. The payload structure corresponds basically
to that of remote key-presses in the mousepad-plugin (with the exception of the
"sendAck"-flag) , e.g.:

{
    "key": "a",
    "specialKey": 12,
    "shift": false,
    "ctrl": false,
    "alt": false,
    "sendAck": true
}

If "specialKey" is a valid keycode according to the internal map (1 <= x <= 32),
the event is interpreted as a special event and the contents of "key" are not
considered.

"key" may contain multi-char strings for performance reasons. In that case,
the peer is expected to print the whole string.

If "sendAck" is set to true, the device expects the remote peer to echo the
event in case it could be handled. This can be used to determine whether the
remote device is ready to accept remote keypresses.