Re: [matplotlib-devel] matplotlib backend_wx

[John H. <jdh...@ac...>]

Hi Jim,

I responded to this earlier today on matplotlib-users.  Here is a copy
of my post.  I'm very interested in getting some feedback if you try
the suggestion below.

JDH


>>>>> "Jim" == Jim Benson <jb...@se...> writes:

    Jim> Hi,

    Jim>   I seem to be seeing some extra debug output. I have been
    Jim> using the wx background and the embedding_in_wx.py example as
    Jim> a template for how to make matplotlib plots in an app i'm
    Jim> writing.  This part works great!!  I am however seeing what
    Jim> appears to be a debug flag left on somewhere?

No, this is in the wx code.  I traced it to the line

  wxInitAllImageHandlers()

Miraculously, I commented this out, got rid of the annoying messages,
and fixed the wx exception swallowing bug!  Jeremy and I have been
killing ourselves for about 6 months trying to figure out why backend
wx was swallowing our exceptions, and I can't really convey how happy
I am to have found this.  We have tried all manner of hacks, google
searches and plantive pleas to get our exceptions back to no avail.
It made debugging wx virtually impossible.

Please test this change on your system.  win32 users, I would also be
much obliged if you could try commenting this out on your system to
see if you lose functionality.  On my linux box, the figures came up
as expected, I was able to print to jpg and png, so all looks well.

Note, wxagg is in CVS if you need some of the agg features that native
wx drawing does not provide.  But it looks like all systems are go for
a release next week so you may as well wait.

JDH