Re: Windows don't fully paint on start up

[Nickolai Dobrynin <dobrynin cs uwm edu>]

Thanks to all who had responded to my message below.  Now that I've figured
the problem out, I'd like to share it with you so you wouldn't possibly fall
into the same silly trap.

I should never have called Gtk::Table::attach in the on_map callback
after 'show_all_children' has been called in the same callback.

Basically, I was trying to make it so that calling 'show' on a widget
would get the entire widget displayed, just the way this is done
in Qt.  I find that GTK is somewhat inconsistent in that there are too
many 'show'-calls (show, show_all, show_all_children, show_now), each
serving different purpose.  I'd rather have one single call that would
be intelligent enough to know what to do in each particular context.

Just some random thoughts...


Regards,

Nickolai



On Fri, Sep 16, 2005 at 06:23:07PM -0500, Nickolai Dobrynin wrote:
> 
> I am writing an application that has two windows.  Frequently, one
> or both windows do not get painted properly on start up, in the sense
> that some widgets are missing until, for example, the mouse is moved
> over them.  Once I minimize the window and then maximize it, it repaints
> itself perfectly, and the problem goes away for this particular run.  So,
> what I have is a start up problem.
> 
> Furthermore, this problem doesn't happen quite as often if I sleep for some
> time after showing the windows but before the main event loop has been
> entered.
> 
> Finally, this problem seems to only be happening on KDE.
> 
> The way I see it is as though there is some race condition somewhere in
> the library.  Anybody could please suggest what may be the cause for this,
> or, if not, if there is any work around.
> 
> 
> Best regards,
> 
> Nickolai