Ugh. Worse than I thought. AFAIK, RFB doesn't support any kind of
XINPUT-style event structure. The RFB PointerEvent simply encapsulates
a button mask and an X and Y position. A new message type, and possibly
multiple new message types, would be needed to support a 3D mouse.
On 10/8/13
Whew. So, for starters, I confirmed the behavior you're observing, but
to figure out why it's happening required trolling the commit logs from
a few years back.
ALR used to be implemented using a second thread, which would wake up
every 100 milliseconds, iterate through all of the active
I am doing research to see the viability of utilizing this software within
my organization. Does anyone have cost analysis or case studies to help
support this? I have read the santos/redhat partnership. Any help would
be greatly appreciated.
