On Mon, 2013-10-14 at 18:13 +0100, Richard Shann wrote:
It
simply shouldn't be possible for the cursor animation to slow things
up,
as you describe since the re-draw requests are queued so that if the
machine is so busy that by the time the draw happens it is too late
then
all that will result is that the steps of the animation will be
skipped
(because it looks at the time and decides which step it should draw).
(It doesn't know that there are steps, just knows what it should draw
at
a given number of milliseconds after the start, too late and it should
just draw the final result).
I wrote the above from memory, but I have just been checking the code
and find it is quite untrue :(
In fact most of these transitions are 10 steps taken at 20 ms intervals
and the steps will be delayed by other things going on.
Which only leaves the question - what else do you have going on? The top
command might help...