> I will have a look at the code for both PyGTK and OS X.
> Hopefully that will show me more of the best way of
> handling this.
The code in PyGTK is a bit easier to understand than the code for OS X. The OS
X code also includes stuff to handle SIGINTs (keyboard interrupts by ctrl-c),
which is
Michiel,
Thanks for jumping into the discussion.
> I wrote the code in PyGTK that uses PyOS_InputHook for interactivity, as well
> as the Mac OS X native backend for matplotlib that uses PyOS_InputHook in
> exactly the same way. PyQT and Tkinter also use PyOS_InputHook, though the
> code is a
Hi Brian,
I wrote the code in PyGTK that uses PyOS_InputHook for interactivity, as well
as the Mac OS X native backend for matplotlib that uses PyOS_InputHook in
exactly the same way. PyQT and Tkinter also use PyOS_InputHook, though the code
is a bit kludgy on Windows. So I definitely agree tha
On Sun, Feb 08, 2009 at 04:08:31PM -0800, Brian Granger wrote:
> * In the current matplotlib backend wx.Yield() is called in a way that
> is not safe as far as protecting against recursive calls to Yield. I
> think it should be called in this way:
> app = wx.GetApp()
> if app is not None:
> app
