Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!udel!haven!decuac!shlump.nac.dec.com!riscy.enet.dec.com!fuel.dec.com!graham
From: graham@fuel.dec.com (kris graham)
Newsgroups: comp.windows.x.motif
Subject: Re: Determining children widget IDs (Summary)
Message-ID: <1859@riscy.enet.dec.com>
Date: 5 Jan 91 06:08:11 GMT
References: <1991Jan2.185621.20296@sctc.com> <20.277b089c@idicl1.idi.battelle.org> <21.277e1314@idicl1.idi.battelle.org>
Sender: newsdaemon@riscy.enet.dec.com
Organization: Mind Terroists
Lines: 28


> One of the OSF/Motif 1.0 manuals had a demo program which did include
> both, and this lead to much frustration later on when  I found out
> that some fucntion protocols (e.g. XtScreen, XtDisplay,..) in Intrinsic.h 
> were being redefined by
> macro defines in IntrinsicP.h by #include-ing the former followed by the
> latter, and this resulted in core dumps when I tried using the functions.

The  XtDisplay ..etc function causing core dumps is a  behaviour ;-) 
that was introduced with the advent of X11R4/Motif 1.1.  There are 
some talks about incompatible specs between R3 and R4.
  
I noticed this  too when moving some applications from Motif 1.0.x to 1.1.

Use  XtDisplayOfObject()  to get around this problem.

 XtDisplayOfObject(object)  

Widget object ;   /*  object whose display is to be returned */


Christopher Graham          
Digital Equipment Corp            
Ultrix Resource Center                                             
New York City

Internet: graham@fuel.enet.dec.com 
UUCP:     ...!decwrl!fuel.enet.dec.com!graham