Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU
Newsgroups: comp.windows.x
Subject: Re: Programs relying on app-defaults files
Message-ID: <8905261605.AA02027@expire.lcs.mit.edu>
Date: 26 May 89 16:05:18 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 13

Independent of whether or not this is an important issue, it's very unlikely
(given present commitments) that this issue will be addressed in the next
version of the Intrinsics.

Here's one thing it seems like you can do.  Put a magic resource in your
app-defaults file.  Have your application check to see if it exists in
the resource database (right after calling XtDisplayInitialize).  If it
doesn't, get the database (with XtDatabase) and merge in whatever resources you
care to (using Xlib routines).  This won't give you exactly the same semantics,
but it should allow you to cope with a missing app-defaults file.

One bug with this approach is that, in R3, XtDatabase apparently can return
NULL if no resources at all were found.  Fixed in next release.