Why does the mouse stop moving when desktop comp is off and you minimize a window?

[soccerballtux]

It stops moving (visibly) during the minimize process and then disappears from where it was and appears where you've moved it to.

 

[Bubbaleone]

😕......"when desktop comp is off"......not clear at all what you're asking.

 

[soccerballtux]

desktop composition. Windows 7/Vista.

 

[Nothinman]

Most likely the system is too busy drawing the minimize animation to handle moving the mouse smoothly. Once that finishes the mouse interrupts are processed and the pointer location updated.

 

[soccerballtux]

Most likely the system is too busy drawing the minimize animation to handle moving the mouse smoothly. Once that finishes the mouse interrupts are processed and the pointer location updated.

that doesn't make sense with 1. quad core 4ghz and 2. windows XP did it just fine

 

[Nothinman]

that doesn't make sense with 1. quad core 4ghz and 2. windows XP did it just fine

It does if you understand how interrupts work. When a driver is working inside of an interrupt nothing else happens, so if that driver works in it's core interrupt handler for more than a ms or 2 you notice lag or jumpiness. Obviously that's either a bug or just bad design of a driver, but it doesn't matter how many cores you have with a shitty driver like that.

And comparing XP to Win7 isn't valid either because they're so different. It's like complaining that your Ford F350 doesn't handle as nice as your old Datsun. Sure they're both vehicles and you might even consider both trucks but they're not even in the same class.

The short version is just that it's a driver issue, the real root cause really only matters to the driver developers.

 

[Lorne]

There is also the issue with W7 doing 2D-3D conversion lag, Its an ongoing problem and is more significant with AMD gfx then Nvidia but only marginal. (Since gfx card mfg have pushed D3D so much they left D2D behind and combined with W7 conversion issue its more noticable)

A way to test this is open task manager and close it and repeat the problem again.
Toms Hardware was looking into this sometime back and nothing new info since.

 

[soccerballtux]

There is also the issue with W7 doing 2D-3D conversion lag, Its an ongoing problem and is more significant with AMD gfx then Nvidia but only marginal. (Since gfx card mfg have pushed D3D so much they left D2D behind and combined with W7 conversion issue its more noticable)

A way to test this is open task manager and close it and repeat the problem again.
Toms Hardware was looking into this sometime back and nothing new info since.

this might explain why I don't see it on other computers.

 

[Nothinman]

There is also the issue with W7 doing 2D-3D conversion lag, Its an ongoing problem and is more significant with AMD gfx then Nvidia but only marginal. (Since gfx card mfg have pushed D3D so much they left D2D behind and combined with W7 conversion issue its more noticable)

A way to test this is open task manager and close it and repeat the problem again.
Toms Hardware was looking into this sometime back and nothing new info since.

Interesting, I hadn't realized the manufacturers had been scaling back the 2D portions of their cards/drivers so much.