Which example file are you using were you see a
> difference?
It appears to be a problem with pylab scripts, eg
> python2.3 examples/simple_plot.py -dWXAgg
I am pretty sure this is a 2.4 versus 2.5 problem. I installed wx 2.4
in my python2.4 tree and 2.5 in my python2.3 tree and find that the
size was wrong only on wx2.4.
This was also true for matplotlib-0.74 and CVS which includes your
patch, so it is not something that was caused by your patch, but it is
a bug.
Since it only occurred for pylab mode and not apps, I poked around the
embedding examples to see what the difference was, and found that the
embedding examples passed the size kwarg to the wx.Frame.__init__
function.
So I added these lines to FigureFrameWx
class FigureFrameWx(wx.Frame):
def __init__(self, num, fig):
...snip...
l,b,w,h = fig.bbox.get_bounds()
wx.Frame.__init__(self, parent=None, id=-1, pos=pos,
title="Figure %d" % num,
size=(w,h))
which appears to work for wx2.4 and 2.5.
So I think all the known problems with wx are fixed for now.
JDH
Hi John,
John Hunter wrote:
"Werner" == Werner F Bruhin <werner.bruhin@...185...> writes:
> Which example file are you using were you see a
> difference?
It appears to be a problem with pylab scripts, eg
> python2.3 examples/simple_plot.py -dWXAgg
I am pretty sure this is a 2.4 versus 2.5 problem. I installed wx 2.4
in my python2.4 tree and 2.5 in my python2.3 tree and find that the
size was wrong only on wx2.4.
This was also true for matplotlib-0.74 and CVS which includes your
patch, so it is not something that was caused by your patch, but it is
a bug.
Since it only occurred for pylab mode and not apps, I poked around the
embedding examples to see what the difference was, and found that the
embedding examples passed the size kwarg to the wx.Frame.__init__
function.
So I added these lines to FigureFrameWx
class FigureFrameWx(wx.Frame):
def __init__(self, num, fig):
...snip...
l,b,w,h = fig.bbox.get_bounds()
wx.Frame.__init__(self, parent=None, id=-1, pos=pos,
title="Figure %d" % num,
size=(w,h))
which appears to work for wx2.4 and 2.5.
So I think all the known problems with wx are fixed for now.
Great.
I am looking at the py2exe optimize problem, would be nice if this could be fixed somehow too.
See you
Werner
···
JDH