On lundi 17 novembre 2008, Frédéric wrote:
> GtkWarning: gtk_widget_set_events: assertion `!GTK_WIDGET_REALIZED
> (widget)' failed
As far as I understand, this assertion is raised because the set_events()
method should be called *after* the widget is realized, ie after it is
drawn on the screen.
But my drawing area is part of a dialog, and this dialog is opened from the
main window as a modal dialog, calling its run() methog. Once it enters in
its main loop, I can't do anything more, so I can't call the set_events()
method!
I don't understand why GTK+ is so complicated for such simple things... Why
signals are not enabled by default? As long as there are no callback, I
don't see what could happen. In fact, I think that low-level stuffs are
not object-oriented, and are very difficult to integrate in an
object-oriented application.
Any idea to solve my problem?
--
Frédéric
http://www.gbiloba.org
_______________________________________________
pygtk mailing list [email protected]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://faq.pygtk.org/
