Hi David, thanks for that, but can you further elucidate? do you know why is this so? in that, how was it decided that a GtkDrawingArea would auto-create these events for itself while a GtkImage widget does not? and am i missing something in the documentation? how could one, from the documentation, know for which widgets this is true? this is essentially hans' question, why is there no widget/signal matrix in the documentation letting us know exactly how these are all mapped between each other? is this a mere oversight, or is there some rhyme and reason going on i don't get? thanks for any further info you might have, richard On Oct 21, 2006, at 9:52 AM, David Nečas (Yeti) wrote: > On Sat, Oct 21, 2006 at 08:00:46AM +0200, Richard Boaz wrote:>>> On Fri, 2006-10-20 at 22:24 +0200, Hans Oesterholt-Dijkema wrote:>>>> Well, I don't get configure events on:>>>>>>>> GtkHBox>>>> GtkEventBox>>>> GtkScrolledWindow>>>> GtkImage.>>>>>>>> So that doesn't work.>>>>>> correct. configure_events are sent only to Gtk::Window's>>>> not true. configure events are nicely delivered to a >> GtkDrawingArea which>> is nothing but a GtkWidget from what the documentation tells me.>> GtkDrawingArea synthetizes configure events and sends them> to itself.>> Yeti>>> --> Whatever.> _______________________________________________> gtk-list mailing list> gtk-list@xxxxxxxxx> http://mail.gnome.org/mailman/listinfo/gtk-list> _______________________________________________gtk-list mailing listgtk-list@xxxxxxxxxxxxx://mail.gnome.org/mailman/listinfo/gtk-list
