James Henstridge [EMAIL PROTECTED] writes:
As for doing a python no op, I have no idea how python triggers the
calling of signal handlers
The signal handlers are queued up somewhere; Python will empty the
queue as soon as it gets the chance -- I'm certain of that. A no-op
would be quite
Aaron Optimizer Digulla [EMAIL PROTECTED] writes:
The only solution I see is to add a timer:
def wakeup:
pass
timeout_add (100, wakeup)
I know of this solution and I will not use it, because it disallows my
program from ever being swapped out -- it continually consumes CPU
Quoting Hrvoje Niksic [EMAIL PROTECTED]:
(does it have anything to do with the threading code?).
I don't think so, no.
Yes, that's the same. Threading doesn't work with the current
implementation of Gtk because all Python threads are dead as long as
Gtk waits in its mainloop for
Do you get the same errors if you call set_active before connecting to its
signals? That is what I usually do. The way you have your code, that
page of the property box will always look as if it has had changes applied
to it, since the call to changed() will always be made.
As for the
Yeah I know ... I put it there. Anyhow, you aren't supposed to be looking
in that directory right now :) The copy in /pub/GNOME/sources/latest is
the same, except for the version number.
James Henstridge.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On Thu, 25 Feb 1999,
