Path: utzoo!attcan!uunet!samsung!usc!snorkelwacker!bloom-beacon!ATHENA.MIT.EDU!swick
From: swick@ATHENA.MIT.EDU (Ralph Swick)
Newsgroups: comp.windows.x
Subject: Re: No expose event for newly created widget
Message-ID: <9008071648.AA17794@lyre.MIT.EDU>
Date: 7 Aug 90 16:48:32 GMT
References: <1990Aug2.230026.5727@tolerant.com>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 19


    The children are positioned by the parent's expose procedure,

This sounds like a mistake.  There are a variety of ways in which
the parent's size can change without generating an expose event.
At minimum, you should [also] position the children in the
parent's change_managed and resize procedures.

    ...after the tree is realized -- in the process of adding
    children to an existing parent -- an expose event for only one child is
    generated.  Neither the parent nor the other children get exposed.

Unless a sibling was obscured and then uncovered by the new child,
or was itself resized, there's no reason to expect exposure events
for the other children.  If the new child completely obscures the
new bits added to the parent's shape, then no exposure event will be
generated for the parent either.

I guess we can't help you without more information.