I've come up with an acceptable solution to my problem, which I'll post here
for posterity. First my observations:
- The expose signal for the container was emitted only once, and after all the
widgets had been added/removed. This is good and means GTK is being smart,
and that
Hi,
This sounds like a very similar problem I'm having. I'm curious if you
have some test case code that you could
post?
thanks,
Todd
Stephen Bach wrote:
I've come up with an acceptable solution to my problem, which I'll post here
for posterity. First my observations:
- The expose signal for
Hi Todd,
This sounds like a very similar problem I'm having. I'm curious if you
have some test case code that you could
post?
My testing was all done within the context of my program, but I can try. The
containers in question are WrapBox, which I've based on the GtkWrapBox class
from Gimp
Hello,
I have a container which periodically loses some of its widgets and gains
others, sometimes on the order of hundreds. The changeover happens all at
once (i.e. there's a big loop which does all the adding and destroying), but
it's still pretty ugly and slow because sometimes many repaints
BTW, I'm writing towards GTK+ 2.4.
On Sat, Aug 21, 2004 at 02:16:52PM -0400, Stephen Bach wrote:
Hello,
I have a container which periodically loses some of its widgets and gains
others, sometimes on the order of hundreds. The changeover happens all at
once (i.e. there's a big loop which
I have a container which periodically loses some of its widgets and gains
others, sometimes on the order of hundreds. The changeover happens all at
once (i.e. there's a big loop which does all the adding and destroying), but
it's still pretty ugly and slow because sometimes many repaints are
When I say repaint I just mean that the there is a visible change in the
widget. I guess I'm not using the word in its conventional GTK sense.
FWIW, I did connect to the expose signal of the container and found that it's
only called once, after the widget switchover is finished. Which I guess
