Paul
It is slowly becoming clearer thanks to you. We can draw
on a pixmap which is associated with a window which
is part of a drawing area.
Configure/Expose events that *just* modify pixmaps work
great. I assume at the end of one of those callbacks
that some hidden routine says, OK, now we
From: Christian Seberino [EMAIL PROTECTED]
Paul
It is slowly becoming clearer thanks to you. We can draw
on a pixmap which is associated with a window which
is part of a drawing area.
Configure/Expose events that *just* modify pixmaps work
great. I assume at the end of one of those
Hi,
Christian Seberino [EMAIL PROTECTED] writes:
It is slowly becoming clearer thanks to you. We can draw
on a pixmap which is associated with a window which
is part of a drawing area.
Configure/Expose events that *just* modify pixmaps work
great. I assume at the end of one of those
Sven
Thanks! I'm getting the impression NOTHING should be
done in configure_handler. Why even bother to
bind it to *anything* then? Am I wrong?
Chris
On Tue, Mar 12, 2002 at 09:29:08PM +0100, Sven Neumann wrote:
Hi,
Christian Seberino [EMAIL PROTECTED] writes:
It is slowly becoming
Ron
Thanks for the reply. It seems that NOTHING should be
done in configure event handler. I'm wondering why
even bind it to ANY function!?!?!?
This is why I'm confused by suggestion to add
gdk_draw_pixmap to configure event handler. Do you
mean (or is it OK) to do drawing in expose event
From: Christian Seberino [EMAIL PROTECTED]
Thanks for the reply. It seems that NOTHING should be
done in configure event handler. I'm wondering why
even bind it to ANY function!?!?!?
If you care specifically about the user resizing or moving your
window, it's useful. It's not really
Hi,
Christian Seberino [EMAIL PROTECTED] writes:
Thanks! I'm getting the impression NOTHING should be
done in configure_handler. Why even bother to
bind it to *anything* then? Am I wrong?
there are cases where it makes sense to use the configure event
but in most cases you just ignore it
