Path: utzoo!attcan!uunet!munnari.oz.au!uhccux!ames!ncar!ico!auto-trol!marbru
From: marbru@auto-trol.UUCP (Martin Brunecky)
Newsgroups: comp.windows.x
Subject: Re: Problem in XtNameToWidget
Message-ID: <1176@auto-trol.UUCP>
Date: 1 Jun 90 15:31:01 GMT
References: <8181@jpl-devvax.JPL.NASA.GOV> <9005301627.AA26071@expo.lcs.mit.edu>
Reply-To: marbru@auto-trol.UUCP (Martin Brunecky)
Organization: Auto-trol Technology, Denver
Lines: 24

In article <9005301627.AA26071@expo.lcs.mit.edu> converse@EXPO.LCS.MIT.EDU (Donna Converse) writes:
>
>It will seg fault if you give it a non-widget argument in the first
>parameter.  The spec stipulates that it will take a non-widget argument,
>so this is a bug in the code.  Since Objects can not and will not ever 
>have children....


   STOP here ! Why ?  Motif "flavor" of R3 Xt had a concept of compositeObject.
   A very usefull feature - at least when you want to REALLY start using
   Xt geometry management. By that I mean far more intelligent geometry
   managers than what's currently around ( attached boxes and row columns ).
   Geometry managers used in nested combinations, so that the geometry
   negotiation really takes place.
   In such configurations you may end up having several layers of pure
   geometry management objects - with no need for a window at each of them.
   Thus, PLEASE, don't rule out composite objects - not yet !


-- 
=*= Opinions presented here are solely of my own and not those of Auto-trol =*=
Martin Brunecky                   marbru@auto-trol.COM
(303) 252-2499                    {...}ncar!ico!auto-trol!marbru
Auto-trol Technology Corp. 12500 North Washington St., Denver, CO 80241-2404