Since KWin decided to use journalctl to record script output, if we want to record mouse locaion rapidly (e.g., using /dev/uinput to simulate a absolute mouse move), the log file blows up to hundered MBs.
I wonder if there is some alternative approaches that is feasable. For example, running a backend with root permissions that could obtain kwin's mouse location with libc::process_vm_readv.
Since KWin decided to use journalctl to record script output, if we want to record mouse locaion rapidly (e.g., using /dev/uinput to simulate a absolute mouse move), the log file blows up to hundered MBs.
I wonder if there is some alternative approaches that is feasable. For example, running a backend with root permissions that could obtain kwin's mouse location with
libc::process_vm_readv
.I performed some attempt, and got this
Feel free to copy the code into your project:)