Re: [matplotlib-devel] Unnecessary rerendering in wx/wxagg backends

2008-04-14 Thread Christopher Barker
Ted Drain wrote: > Just a note about the speed of blitting: Your points are well taken. I had forgotten about remote X sessions, and yes, if you need to convert to a different type of pixmap, that can take time too, so keeping it to just what's needed does make sense. -Chris -- Christopher

Re: [matplotlib-devel] Unnecessary rerendering in wx/wxagg backends

2008-04-14 Thread Ted Drain
[matplotlib-devel] Unnecessary rerendering in wx/wxagg > backends > > Hi Christopher, > > thanks for your valueable feedback. I am proceeding slowly, but > steadily. > > > > > backend_qtagg.py seems to contain a proper (more or > >> less, see other postings

Re: [matplotlib-devel] Unnecessary rerendering in wx/wxagg backends

2008-04-14 Thread Gregor Thalhammer
Hi Christopher, thanks for your valueable feedback. I am proceeding slowly, but steadily. > > > backend_qtagg.py seems to contain a proper (more or >> less, see other postings of Ted Drain) implementation of double >> buffered drawing that avoids unnecessary rerendering of the bitmap. > > It stil

Re: [matplotlib-devel] Unnecessary rerendering in wx/wxagg backends

2008-04-10 Thread Christopher Barker
Gregor, Thanks for working on this. > backend_qtagg.py seems to contain a proper (more or > less, see other postings of Ted Drain) implementation of double buffered > drawing that avoids unnecessary rerendering of the bitmap. It still feels a bit kludgy to me -- a paint event should simply copy

Re: [matplotlib-devel] Unnecessary rerendering in wx/wxagg backends

2008-04-07 Thread Gregor Thalhammer
Here I attached diff files of my changes, compared to matplotlib-0.91.2 release. Gregor Thalhammer --- Kopie von backend_wx.py Mon Mar 31 10:28:22 2008 +++ backend_wx.py Sun Apr 6 10:23:09 2008 @@ -752,11 +752,14 @@ self._isRealized = False self._isConfigured = False

Re: [matplotlib-devel] Unnecessary rerendering in wx/wxagg backends

2008-04-07 Thread Gregor Thalhammer
I continued to work on this issue. Thanks for Chris Barker for pointing me into the right direction. I also had a look at other gui backends, and, among other, backend_qtagg.py seems to contain a proper (more or less, see other postings of Ted Drain) implementation of double buffered drawing th

Re: [matplotlib-devel] Unnecessary rerendering in wx/wxagg backends

2008-03-31 Thread Christopher Barker
Erik Tollerud wrote: > I tested this on 0.91.2 on Ubuntu Gutsy, and wx 2.8.7.1, and found > that when I bring up a new window, I see a black canvas and it doesn't > draw any of the matplotlib objects until I do something like resizing > that must explicitly call a draw at some point. yup, same her

Re: [matplotlib-devel] Unnecessary rerendering in wx/wxagg backends

2008-03-31 Thread Erik Tollerud
I tested this on 0.91.2 on Ubuntu Gutsy, and wx 2.8.7.1, and found that when I bring up a new window, I see a black canvas and it doesn't draw any of the matplotlib objects until I do something like resizing that must explicitly call a draw at some point. This may be why it's in there... perhaps s

[matplotlib-devel] Unnecessary rerendering in wx/wxagg backends

2008-03-31 Thread Gregor Thalhammer
Dear developers, I discovered that in backend_wx.py in _onPaint(), the callback function for repainting a matplotlib figure, every time a repaint is done also the bitmap is rerendered: backend_wx.py/_onPaint(): ... # Render to the bitmap self.draw(repaint=False) ... This also affects the behav