Xpra: Ticket #137: games rely on precise mouse movements and their timing
effectively, they do their own mouse acceleration, and since we send the mouse movements packets when we feel like it, the games see jerky mouse movements and produce jerky mouse movements in the game...
queue_mouse_position_packet only keeps one mouse "positional" packet at a time, so we only send the last one rather than all the mouse movements.
There will be a high cost when sending all mouse movements, so this will need to be an option.
First thing to do is to try to replace
Sun, 03 Jun 2012 16:56:49 GMT - Antoine Martin: status, description changed
changed from new to accepted
Sun, 03 Jun 2012 17:28:52 GMT - Antoine Martin: owner, status changed
changed from Antoine Martin to ahuillet
changed from accepted to assigned
Thu, 27 Sep 2012 15:22:05 GMT - Antoine Martin: milestone changed
changed from 0.4 to future
Mon, 08 Oct 2012 10:49:36 GMT - Antoine Martin:
Some potentially relevant pointers and thoughts:
- maybe using a different mouse type, a tablet or something that uses absolute positioning would prevent the games/libraries from doing pointer acceleration on our events - which are always lagging by a variable amount of time
- maybe using a different API than Xtest? see below.
- a number of api calls below support a delay parameter, we could set our internal target delay to something close to the highest client latency observed (or 90 percentile?) and then adjust the api delay on our simulated events so that all the events have the same gap between them as on the client. (and if we suddenly get a higher client latency.. increase the target delay to accommodate and go back down slowly?) - should work?
Wed, 10 Oct 2012 06:18:30 GMT - Antoine Martin: version changed
changed from 0.3.x to trunk
Fri, 16 Jan 2015 10:54:39 GMT - Antoine Martin:
See also #770 and in particular r8482 which added
Mon, 01 Feb 2016 18:02:44 GMT - urzds: cc set
Sun, 26 Nov 2017 14:01:35 GMT - Antoine Martin:
See also #173
Mon, 22 Jan 2018 06:08:11 GMT - Antoine Martin: status changed; resolution set
changed from assigned to closed
set to wontfix
The !XTest extension is being deprecated, so the way forward is going to be #173.
Sat, 23 Jan 2021 04:46:32 GMT - migration script:
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/137