My problem is simple and can be illustrated in 5 minutes (probably less if you frequently use WPF) of coding:
Create a WPF window (3.0/3.5/maybe 4.0). Put a grid on it, and put a rectangle in the grid. Implement code to make one of the rectangles follow the mouse cursor on the (window's or grid's) MouseMove event by setting the rectangle's Margin or
RenderTransform. Everything looks nice when it runs.
Now add a second object to the grid that can animate (either another rectangle, or even a button that uses the aero theme because the blue glowing is handled through animations). Do something so that the second object animates continuously. Now
run it again. The first rectangle lags the mouse cursor by a substantial amount when the animation is occurring. If the animation lasts for a short amount of time (< 500ms), then the lag stops immediately after the animation ends. If the
animation lasts for a long time, then there is a delay between when the animation stopped and when the lag stopped. Sometimes this extra delay lasts for a very long time (> 10 sec).
I have asked people more knowlegable than myself, and I have spent a lot of time on google looking for information. I want to know if anyone can explain these effects. An easy fix would be to not use animations where this would be a problem,
View Complete Post