Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!TUB.BITNET!net
From: net@TUB.BITNET (Oliver Laumann)
Newsgroups: comp.windows.x
Subject: Re: XtMainLoop -vs- XtAppMainLoop
Message-ID: <8812191733.AA29725@tub.UUCP>
Date: 19 Dec 88 17:33:02 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 24

> > you can replace the call to
> > XtCreateApplicationContext by a call to _XtDefaultAppContext ...
>
> Using XtWidgetToApplicationContext() on the shell returned by
> XtInitialize() would be much better.

The original article discussed a scenario where a client calls
XtToolkitInitialize, XtCreateApplicationContext, and XtAppCreateShell
explicitly (the usual way to initialize an application if one wants to
make use of application contexts).  In this case,
XtWidgetToApplicationContext does not return the default application context.

Is using `XtInitialize' still a `sanctioned' way to initialize an application
under Release 3, or is it likely to become obsolete in future releases?

Anyway, the existence of an automatically created default application
context and the co-existence of `XtAddFoo' and `XtAppAddFoo' functions
is a mess (there is not even a corresponding XtAddFoo for each XtAppAddFoo!).
Resource converters should be made a global resource (I don't see a reason
why they are stored in application contexts).

Regards,
--
Oliver Laumann              net@TUB.BITNET              net@tub.UUCP