This isn't really an issue if spice-record is the only client, because it never sends any cursor position updates to the VM. (Unless I suppose someone is programatically moving the cursor.)
However, with multi-client support, it would be useful to see where the other client is moving his mouse.
This isn't really an issue if spice-record is the only client, because it never sends any cursor position updates to the VM. (Unless I suppose someone is programatically moving the cursor.)
However, with multi-client support, it would be useful to see where the other client is moving his mouse.
It looks like we can handle here the new
CursorChanneland then watch for thecursor-movesignal.