James Henstridge writes:
It provides a non GUI base for objects. I have been wondering about
whether to put the base gobject support into a separate module or not, and
whether I should keep it separate from the gtk package (when you import
gtk, it initialises the GUI). Does this sound
1)
I was having awful problems trying to get x-input
extension events to register.
Turns out, all the connections and set_event calls
must be done prior to calling a widget's show().
Doh!
Is this true of all handling? I find I get very
different results if I register events before
or after a
James Henstridge writes:
Well, this is one of those things where we won't know how many useful non
gui libraries will use the object model until after the glib/gtk 2.0
release. I have decided to put the GObject wrapper stuff in a separate
module just in case.
There's certainly no way
On Mon, 26 Jun 2000, Fred L. Drake, Jr. wrote:
For quite a while, I have been passing function pointers around as
CObjects in the modules (eg. gtk._gtk._PyGtk_API in the 0.7.0 release),
which means that the different wrapper modules don't need to see each
other's symbols.
