By doing this I found a few more oversights (wx to wx.) in
> backend, updated version is attached.
OK, I've got it working with wxpython 2.5.5.1
The only glitch I've noticed so far is that the figsize parameter does
not appear to be respected. The windows that are created a
considerably smaller than they should be.
Any ideas?
JDH
Hi John,
John Hunter wrote:
"Werner" == Werner F Bruhin <werner.bruhin@...185...> writes:
> By doing this I found a few more oversights (wx to wx.) in
> backend, updated version is attached.OK, I've got it working with wxpython 2.5.5.1
The only glitch I've noticed so far is that the figsize parameter does
not appear to be respected. The windows that are created a
considerably smaller than they should be.Any ideas?
Only float to int change I did was in the Printer_Print method to remove a deprecation warning.
I'll have another look this afternoon.
JDH
See you
Werner
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Hi John,
John Hunter wrote:
"Werner" == Werner F Bruhin <werner.bruhin@...185...> writes:
> By doing this I found a few more oversights (wx to wx.) in
> backend, updated version is attached.OK, I've got it working with wxpython 2.5.5.1
The only glitch I've noticed so far is that the figsize parameter does
not appear to be respected. The windows that are created a
considerably smaller than they should be.Any ideas?
Just did a little test, copied back the originals for backend_wx and backend_wx_agg and run embedding_in_wx4 and the figure size in both cases is about 390x318.
Which example file are you using were you see a difference?
BTW, also noticed with the embedding_in_wx4 the CPU usage stays at 100% and I can't close it (at least not always) - again with original or modified code.
JDH
See you
Werner
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Hi John,
Werner F. Bruhin wrote:
Hi John,
John Hunter wrote:
"Werner" == Werner F Bruhin <werner.bruhin@...185...> writes:
> By doing this I found a few more oversights (wx to wx.) in
> backend, updated version is attached.OK, I've got it working with wxpython 2.5.5.1
The only glitch I've noticed so far is that the figsize parameter does
not appear to be respected. The windows that are created a
considerably smaller than they should be.Any ideas?
Just did a little test, copied back the originals for backend_wx and backend_wx_agg and run embedding_in_wx4 and the figure size in both cases is about 390x318.
Which example file are you using were you see a difference?
BTW, also noticed with the embedding_in_wx4 the CPU usage stays at 100% and I can't close it (at least not always) - again with original or modified code.
To correct the CPU usage change the OnPaint event to include an event.Skip() as this:
def OnPaint(self, event):
self.canvas.draw()
event.Skip()
That also makes the toolbar show up correctly.
See you
Werner
JDH
See you
Werner-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Hi John,
I actually think that the OnPaint event in embedding_in_wx is not needed at all.
See you
Werner
Werner F. Bruhin wrote:
Hi John,
Werner F. Bruhin wrote:
Hi John,
John Hunter wrote:
"Werner" == Werner F Bruhin <werner.bruhin@...185...> writes:
> By doing this I found a few more oversights (wx to wx.) in
> backend, updated version is attached.OK, I've got it working with wxpython 2.5.5.1
The only glitch I've noticed so far is that the figsize parameter does
not appear to be respected. The windows that are created a
considerably smaller than they should be.Any ideas?
Just did a little test, copied back the originals for backend_wx and backend_wx_agg and run embedding_in_wx4 and the figure size in both cases is about 390x318.
Which example file are you using were you see a difference?
BTW, also noticed with the embedding_in_wx4 the CPU usage stays at 100% and I can't close it (at least not always) - again with original or modified code.
To correct the CPU usage change the OnPaint event to include an event.Skip() as this:
def OnPaint(self, event):
self.canvas.draw()
event.Skip()That also makes the toolbar show up correctly.
See you
WernerJDH
See you
Werner-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click