traceback with error/warning messages

wxPython Users
1

Jean Brouwers wrote:

After more web searching, I found some promising information on this issue.

It turns out that GTK recognizes a command line option --g-fatal-warnings.
With this option set, GTK calls abort() after printing a warning message.

<http://www.localhost.nl/stuff/gtk/gtk_tut-2.html&gt;

That is the easy part. The two main questions are (1) how to pass a command
line option to GTK, specifically to the gtk_init() call and (2) how to handle the
abort() call from GTK.

On (1), the gtk_init() function is called by the wxEntryStart() function in the
wxPython file src/gtk/app.cpp. It looks like the command line options are passed
to wxEntryStart() in the argc and argv arguments. However, it's unclear where
wxEntryStart() is called from.

It's called from within the wx.PyApp.__init__. The values in sys.argv will automatically be converted into the form needed so you should just need to put the value on your app's command-line.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

2

Jean Brouwers wrote:

It's called from within the wx.PyApp.__init__. The values in sys.argv will automatically be converted into the form needed so you should just need to put the value on your app's command-line.

GTK does, but I don't know which ones. Does it make any difference if you do your signal binding before or after the wx.App object has been created?

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!