1631ada5b3
- 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 |
||
|---|---|---|
| .. | ||
| abstractremoteinput.cpp | ||
| abstractremoteinput.h | ||
| CMakeLists.txt | ||
| config-mousepad.h.cmake | ||
| kdeconnect_mousepad.json | ||
| macosremoteinput.h | ||
| macosremoteinput.mm | ||
| mousepadplugin.cpp | ||
| mousepadplugin.h | ||
| README | ||
| waylandremoteinput.cpp | ||
| waylandremoteinput.h | ||
| windowsremoteinput.cpp | ||
| windowsremoteinput.h | ||
| x11remoteinput.cpp | ||
| x11remoteinput.h | ||
When the user moves his on the phone, dx and dy (The difference between the last movement and the current movement of the X and Y Axis respectively) is sent inside a NetworkPackage QCursor is used to move mouse cursor according to its relative position. When the user tap or double taps his phone, a mouse key button is simulated using XTestFakeButtonEvent