I guess because in the same system some computers may have a problem and others do not. This would imply a distal rather than a proximal (server) problem.
I agree this is a strong indication. Another indication (but not proof) is other people having performance problems with .NET/Windows Forms applications on XP, i.e. not Amazing Charts.
For example this programmer describes "slow and flickery repainting" and says "It drives me absolutely nuts to see a system with a 3GHz Core 2 and a GeForce 8800 take four seconds to redraw a list view"
This sounds like Amazing Chart's problem. Could possibly be related anyway, no way to say for sure. Anyway he was able to fix the problem by modifying the code, something we can't do.
http://www.virtualdub.org/blog/pivot/entry.php?id=273Here's a more generic article about Windows Forms performance, suggesting there are many different things the programmers can do to address performance. None of them simple I'm sure, but just shows it's a general concern with Window Forms.
http://msdn.microsoft.com/en-us/magazine/cc163630.aspxHere is an interesting one which does mention the "hardware acceleration" fix. He says one tick ABOVE disabled, something I haven't tried.
http://stackoverflow.com/questions/...he-datagridview-on-one-of-my-two-screensNone of this is really that helpful. But maybe the lack of a quick-fix by those suffering from this outside AC says something.
