On Sat, 2005-05-14 at 13:49 +1000, Russell Shaw wrote:
> Why doesn't every widget have an X window?
Read this:
http://primates.ximian.com/~federico/misc/gtk-drawing-model/
It explains this and other things.
Federico
___
gtk-devel-list mailing list
On Sun, 2005-05-15 at 00:03 +1000, Russell Shaw wrote:
> Owen Taylor wrote:
> > On Sat, 2005-05-14 at 13:49 +1000, Russell Shaw wrote:
> >
> >
> >> 2. The need to have windows to catch mouse events in itself
> >>
> >>>is a problem. It's a frequent GTK+ FAQ, GTK+ widgets like
> >>>GtkLab
Owen Taylor wrote:
On Sat, 2005-05-14 at 13:49 +1000, Russell Shaw wrote:
2. The need to have windows to catch mouse events in itself
is a problem. It's a frequent GTK+ FAQ, GTK+ widgets like
GtkLabel have complex logic for sometimes adding an event
widget, and an artificial restriction
On Sat, 2005-05-14 at 13:49 +1000, Russell Shaw wrote:
> 2. The need to have windows to catch mouse events in itself
> > is a problem. It's a frequent GTK+ FAQ, GTK+ widgets like
> > GtkLabel have complex logic for sometimes adding an event
> > widget, and an artificial restriction
Owen Taylor wrote:
Rather then comment on the patch immediately, I thought I'd go back
and try to write up the problems we are trying to solve here in some
detail so I'd have them clear in my own mind.
- Owen
Issues to solve
===
...
2. Th
Rather then comment on the patch immediately, I thought I'd go back
and try to write up the problems we are trying to solve here in some
detail so I'd have them clear in my own mind.
- Owen
Issues to solve
===
There are two basic proble
window created by its parent.
This is needed to make prelighting of notebook tabs possible
(http://bugzilla.gnome.org/show_bug.cgi?id=153966). Without global
motion events, window widgets that didn't select crossing events would
make it impossible for the GtkNotebook to track the cursor.
An
