kdeconnect-kde/plugins/remotekeyboard
Alexander Lohnau 1631ada5b3 Simplify KDEConnectPlugin::recievePacket
- We do not need the return type. If a plugin declares it can handle the
  packet it should do so. We don't have any fallback logic in place and
  the packet types are namespaced with the plugin IDs anyway.

- Provide a default implementation with a warning, not all plugins need
  to overwrite this
2023-08-03 20:49:44 +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-30 01:37:54 +00:00
README Add remotekeyboard plugin 2017-01-23 09:08:27 +01:00
remotekeyboardplugin.cpp Simplify KDEConnectPlugin::recievePacket 2023-08-03 20:49:44 +02:00
remotekeyboardplugin.h Simplify KDEConnectPlugin::recievePacket 2023-08-03 20:49:44 +02:00

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.