On 10/18/2011 06:19 AM, RuiDC wrote: > > As of 1.1.0, FigureCanvasQTAgg.draw() now no longer calls > FigureCanvasAgg.draw(), and as a result I am getting problems with code that > used to update positions/size of legend and labels during on_draw. > > 1. Is there a new way to get the canvas to draw? or is this a bug?
The problem is that all drawing is now deferred until a paintEvent occurs. draw() is using the update() method to queue the request for a paintEvent, where all actual drawing is done, consistent with what I understand to be the recommended mode of operation for QT, but maybe not with the way mpl operates; it has the effect of making draw() work like draw_idle(). It looks like what I should do is move the call to FigureCanvasAgg.draw back into the FigureCanvasQTAgg.draw method. I'll give it a try. Eric > > The "what's new in 1.1.0" page, > http://matplotlib.sourceforge.net/users/whats_new.html refers to: > "An rcParam entry, “backend.qt4”, has been added to allow users to select > PyQt4, PyQt4v2, or PySide." > > 2. I cannot see any reference to PyQt4v2 in the code, and any attempt to set > the rcParam to use it results in a param validation error, is this a mistake > in the web page or omission in the code? > > Thanks in advance > RuiDC ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
