Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!lll-winken!sun-barr!newstop!sun!amdcad!dgcad!dg-rtp!wgate!lanzo
From: lanzo@wgate.UUCP (Mark Lanzo)
Newsgroups: comp.windows.x.motif
Subject: Re: Question about Motif resource converters
Message-ID: <189@atesysv.UUCP>
Date: 5 Jun 91 15:30:40 GMT
References: <188@atesysv.UUCP> <1991Jun3.090811@wsl.dec.com>
Reply-To: lanzo@atesysv.UUCP (Mark Lanzo)
Organization: Wandel & Goltermann Technologies, Inc.
Lines: 40

In a prior article klee@wsl.dec.com wrote:
 ]  In article <188@atesysv.UUCP>, lanzo@wgate.wgate.com (Mark Lanzo) writes:
 ]  |>     What is the correct way to get all of the Motif resource type
 ]  |>     converters registered when my application starts up?
 ]  
 ]  Widget set resource converters are usually registered when the vendor
 ]  shell widget class for that widget set is created.  This is true of
 ]  both the Athena and Motif widget sets.  Normally, the first widget you
 ]  would create is a vendor shell.  Is there some reason you are not?

No there isn't.  As my prior article showed, I call XtInitialize() to
create my first widget.  XtInitialize supposedly creates an ApplicationShell, 
which is subclass of VendorShell.

Part of the point of my prior posting was that I thought it was odd
that I needed to call XmRegisterConverters();  I had expected it to
be implicit with the XtInitialize call (as you have also implied).

This does leave me with a question though:  how does the Intrinsics
function XtInitialize determine that it should be creating the 
(supposedly) libXm-defined widget ApplicationShell?  The documentation 
I have for the Intrinsics lib states that XtInitialize() creates a 
TopLevelShell, but all of the documentation I have on Motif indicates 
that XtInitialize returns an ApplicationShell instead.  I checked libXm.a; 
it does not redefine the function XtInitialize().
Actually, if I do symbol dumps on the libraries, I find that 
applicationShellWidgetClass is defined in libXt.a rather than libXm.a.
Is this the way it is supposed to be?  This means either (a) the
documentation I have is wrong; applicationShells are part of the
Xt Intrinsics, or (b) libXt.a has been tweaked for the benefit of Motif.
If the latter is true, then I would have expected the other functions
to also have been tweaked to correctly do all the extra initialization
required by the Motif library.

Is there (or should there be) some Motif function that takes the place
of XtInitialize?  Motif apparently doesn't supply an analogous routine
to XtInitialize, e.g. XmInitialize.

Perhaps I should go program in MS-Windows instead :-)

			--Mark--