> Maybe I don't understand what the goal is here.
The goal is to get notified by Gdk when a window will not have to draw
itself (e.g. is hidden/invisible or whatever).

I played a bit with the double-buffer implementation and to keep a
single pixmap for the top-level window instead of creating/destroying
a new pixmap for each paint per window.
However now I am searching for a way to release this buffer if I know
for sure that frequent re-paints are unlikely (-> e.g. the window is
hidden).

> If all you want is to know when one of the events in the Subject line
> happens, then the simplest platform independent low-level way to do it
> is the gdk_window_set_filter.
Sorry I thought GdkXEvents are platform depandant. My fault, sorry :-/
... the X confused me ;)
I'll have a look there, thanks a lot!

> My original point was that this information is in the GdkWindow API
> documentation and locating it wasn't hard, even if you know little about
> GTK+.
I understand your rant, and I already studying GTKs reference
frequently hopin to find the bits I am searching for. But its like
double-buffering, the whole painting-process was explained in another
document (thanks a lot, this really helps!) someone on the list told
me.
I found all the gtk hide/show signals but howto do it in Gdk -> then
it becoms a bit dark for an gtk-unexperienced programmer.
Maybe I would need hours/days searching and trying out for finding a
suboptimal solution, which could be answered in one minute on the
list.

lg Clemens
_______________________________________________
gtk-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gtk-list

Reply via email to