Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-beacon!dont-send-mail-to-path-lines
From: randy@erik.UUCP (Randy Brown)
Newsgroups: comp.windows.x
Subject: Re:  Wcl Question
Message-ID: <9105110010.AA20984@erik.uucp>
Date: 11 May 91 00:10:28 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 31


> From: uunet!venice.sedd.trw.com!diaz (Phillip Diaz)

>     appShell = XtAppCreateShell(appName, appClass,
>                                 applicationShellWidgetClass, 
>                                 display, 
>                                 NULL, 0);

> Warning; WcWidgetCreation (xxxxxx) - Failed
>              Problem: No children defined in Xrm database.
>              Possible: resource file not found (XENIRONEMENT not set?),
>              Possible: top level widget in resource file not name xxxxxx
> 
> Error: Shell widget xxxxxx has zero width and/or height

This may be too  simplistic (since I've never tried to do this, I don't
know all the possible errors that can occur), but it's sufficient--
your XtAppCreateShell creates a new root for a widget hierarchy, the
appShell widget.  Its name is *appName.  Suppose that *appName is "newTop".
Do you have a line in your new resource file like

newTop.wcChildren: larry, moe, joe

because if you don't, wcl will not be able to get the subresources of
the shell widget to know what children to create.  (In theory I think
you can use *appClass as well, but I'm not positive.)

Even if you think the line's there, check again.  The worst problem
with the resource database is that there is little error checking; two
of us once spent a long time looking for various problems which turned
out to be caused by wcChildern in place of wcChildren.