Mike,
On 03/05/2013 15:14, Michael Droettboom wrote:
FWIW: Matplotlib uses the older buffer interface because that is what
the older version of wx used (as well as other GUI toolkits). It
would be nice to move to the new memoryview objects, but all of the
GUI frameworks will need to move in t
FWIW: Matplotlib uses the older buffer interface because that is what
the older version of wx used (as well as other GUI toolkits). It would
be nice to move to the new memoryview objects, but all of the GUI
frameworks will need to move in tandem...
Mike
On 04/27/2013 06:23 PM, Werner F. Bruh
Would you mind submitting this as a pull request?
Mike
On 04/27/2013 06:23 PM, Werner F. Bruhin wrote:
Hi Michael,
On 26/04/2013 14:40, Michael Droettboom wrote:
On 04/26/2013 02:57 AM, Werner F. Bruhin wrote:
Hi,
Anyone can provide some info on what "agg.buffer_rgba" returns and
maybe
ev
Hi Michael,
On 26/04/2013 14:40, Michael Droettboom wrote:
On 04/26/2013 02:57 AM, Werner F. Bruhin wrote:
Hi,
Anyone can provide some info on what "agg.buffer_rgba" returns and maybe
even some suggestion on how to resolve this issue in the wxagg backend.
It returns a Python buffer object on
On 04/26/2013 02:57 AM, Werner F. Bruhin wrote:
> Hi,
>
> Anyone can provide some info on what "agg.buffer_rgba" returns and maybe
> even some suggestion on how to resolve this issue in the wxagg backend.
It returns a Python buffer object on Python 2, though on Python 3 it is
a memoryview, since
Hi,
Anyone can provide some info on what "agg.buffer_rgba" returns and maybe
even some suggestion on how to resolve this issue in the wxagg backend.
Thanks
Werner
P.S.
The archive on Sourceforge for this list stops in June 2012, noticed
this as I wanted to check if there are answers I didn't g
Hi,
I am trying to get matplotlib 1.2.0 to work with wxPython Phoenix - will
provide a patch when it is working.
Made the changes to backend_wx* for things like EmptyImage/EmptyBitmap
and Toolbar but I am stuck on the following.
if bbox is None:
# agg => rgba buffer -> bitmap
