Darren Dale a écrit : >> If you need something to prove that this has nothing to do with my >> machine or my software, I can tell you that there is exactly the same >> bug on a virtual machine, after a clean Windows XP install, and using >> only the official Python MSI installer and the official PyQt installer >> (and the latest matplotlib release of course). I also saw the same bug >> on three other machines, but the real proof is the VM. >> > > I'm not familiar with virtual machines, so I guess I dont understand what > that > proves. I'm looking for something that indicates this is an issue with > matplotlib and not Qt. You found a problem once you upgraded from 4.3.3, but > I have not seen a similar problem. I'll try running your test script on a > I've just received another proof (I know that it does not solve the problem, but I'm feeling less lonely!): a canadian Python/Qt user experienced exactly the same bug (and he did the test on three different machines, two with XP and one with Vista). > windows machine tonight, but in the meantime, perhaps you could try to > determine if there is a step in backend_qt4agg.FigureCanvasQTAgg.paintEvent > (or somewhere else) that is the source of the bottleneck. > What do you mean exactly?
Pierre ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
