kdeconnect-kde

History

Alexander Lohnau 02d97aabf4 Add explicit moc includes to cpp files The rationale is explained in https://planet.kde.org/friedrich-kossebau-2023-06-28-include-also-moc-files-of-headers/ In case of KDEConnect, it impressively speeds up compilation. Before it took 390 seconds on a clean build and with this change it took 330 seconds. This is due to the mocs_compilation having to include the header files and thus all their headers. Due to the lots of small plugins we have, this means that the same headers must be compiled plenty of times. When we include the moc files directly in the C++ file, they are already available.		2023-07-28 16:07:34 +02:00
..
CMakeLists.txt	Use target-centric CMake approach for declaring debug category	2023-07-22 20:51:19 +00:00
kdeconnect_remotekeyboard.json	SVN_SILENT made messages (.desktop file) - always resolve ours	2023-07-28 01:41:47 +00:00
README	Add remotekeyboard plugin	2017-01-23 09:08:27 +01:00
remotekeyboardplugin.cpp	Add explicit moc includes to cpp files	2023-07-28 16:07:34 +02:00
remotekeyboardplugin.h	Use pragma once in plugins	2023-07-22 20:51:19 +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.