I have attached the updated backend_wx.py. Obviously if
> I've broken wxGTK I'll need to look into it as a matter of
Probably is a GTK2 thing. Do you have access to a GTK2 machine to
> This sounds worryingly as though you do have the latest
> version (there was no file save dialog code at all until
> this morning).
Yep, same problem with the attached code.
> In particular, the behaviour of a wxMemoryDC (which is the
> context used to draw into the bitmap) seems quite
> different between the two platforms. The main bug I've had
> to deal with is that the bitmap can only be selected into
> a single wxMemoryDC at a time. This means that I have to
> take explicit care to ensure that whenever a
> GraphicsContextWx.new_gc() is called, I explicitly ensure
> that the bitmap is selected from the last wxMemoryDC.
I diagnosed why the print code doesn't save a file. It hangs
indefinitely on the call to
gc = self.drawable.new_gc()
> The other thing to look for is in the _onSize and _onPaint
> methods of FigureWx: the image from the bitmap is sent to
> the screen with a Blit() call. This seems to be necessary
> on Windows as the (simpler, but equivalent) DrawBitmap()
> call does not work properly.
Tried Blit versus DrawBitmap in both. No help
> Where the printing is concerned, again, you could try
> uncommenting the 'self.bitmap.SaveFile()' line, which
> checks whether it is possible to save a 'known good'
No help, due to the hang on new_gc
Any other ideas?