kdeconnect-kde

History

Aleix Pol b61ba29673 remotekeyboard: Move workaround to the c++ side and make it more generic The QKeyEvent::text we get from a Ctrl+W press is a weird unicode charcater for ^W (see comment). We don't deal with that thing, create the controlled letter using QKeySequence and move on.		2023-05-22 17:43:27 +00:00
..
CMakeLists.txt	Adapt build system to also support Qt 6	2022-10-29 16:51:41 +02:00
kdeconnect_remotekeyboard.json	SVN_SILENT made messages (.desktop file) - always resolve ours	2023-02-04 02:05:14 +00:00
README	Add remotekeyboard plugin	2017-01-23 09:08:27 +01:00
remotekeyboardplugin.cpp	remotekeyboard: Move workaround to the c++ side and make it more generic	2023-05-22 17:43:27 +00:00
remotekeyboardplugin.h	Add and make use of ECM's clang-format integration	2022-09-11 23:21:58 +00: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.