[86] in The GTK GIMP ToolKit mailing list archive
[gtk-list] Re: gtk_container_check_resize performance
daemon@ATHENA.MIT.EDU (Peter Mattis)
Sun May 11 15:09:40 1997
To: gtk-list@redhat.com
In-reply-to: Your message of "Sun, 11 May 1997 12:03:31 PDT."
<Pine.BSF.3.91.970511114251.11686A-100000@blacklodge.c2.net>
Date: Sun, 11 May 1997 12:02:17 -0700
From: Peter Mattis <petm@scam.XCF.Berkeley.EDU>
Resent-From: gtk-list@redhat.com
Reply-To: gtk-list@redhat.com
Raph Levien writes:
>BTW, can anyone explain to me the rationale for why a widget should or
>should not have its own window? It is obvious why a viewport should be a
>window (a cheap call to XMoveResizeWindow gets the window scrolled), but
>far less clear why a button needs to be a window. For the time being, I'm
>using ifdefs so I can configure the html container to have its own window
>or not. So far, I can't see any difference, but when I start heavily
>nesting them (because that's how tables are going to work), it will
>probably become more significant.
Events. Events are generated (by X) on windows, so any widget which
wants to handle anything other than the basic exposure events needs to
create a window. In the instance of a button widget, it needs to be
able to get mouse press and release and enter/leave notify events.
Peter
--
To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
