Path: utzoo!attcan!uunet!aplcen!samsung!usc!snorkelwacker!bloom-beacon!eru!luth!sunic!bmc.uu.se!kuling!kuling.docs.uu.se!matsj From: matsj@delfi.UDAC.UU.SE (Mats Johnson) Newsgroups: comp.windows.x Subject: Re: XtRealizeWidget() - Why does it work as it does? Message-ID: Date: 15 Jun 90 12:15:18 GMT References: <30684@cup.portal.com> Sender: news@kuling.UUCP Organization: cmd Lines: 16 In-reply-to: gtc@cup.portal.com's message of 11 Jun 90 02:40:57 GMT In article <30684@cup.portal.com> gtc@cup.portal.com (greg t chalfin) writes: I'm trying to understand how XtRealizeWidget() works, and something seems strange about it. (I'm probably missing something.) ... It maps on the way back up, as the recursive calls return. This means it maps children first and ancestors later. I'd say that's because mapping a child of an unmapped parent does not actually map the child onto the screen, it only has the effect that the child will be mapped whenever the parent is. -- ------ Mats Johnson, UDAC, Box 2103, S-750 02 Uppsala, SWEDEN. Phone +46 18-187858 E-mail: matsj@delfi.UDAC.UU.SE