Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!hplabs!hplabsz!dayoung
From: dayoung@hplabsz.HPL.HP.COM (Doug A. Young)
Newsgroups: comp.windows.x
Subject: Re: Programs relying on app-defaults files (was: Re: xclipboard bug?)
Keywords: app-defaults
Message-ID: <3408@hplabsz.HPL.HP.COM>
Date: 30 May 89 16:48:49 GMT
References: <8905151402.AA06843@THANATOS.MIT.EDU> <773@acorn.co.uk> <1041@sragwa.sra.JUNET> <3401@hplabsz.HPL.HP.COM> <1305@harrier.ukc.ac.uk>
Reply-To: dayoung@hplabsz.UUCP (Doug A. Young)
Organization: Hewlett-Packard Laboratories
Lines: 22

In article <1305@harrier.ukc.ac.uk> rlh2@ukc.ac.uk (Richard Hesketh) writes:
>
>As Bob said this probably won't be included in R4 so having patches to
>the source ain't a good thing ... however because the idea is so simple
>(WDITOT 8-) it can be made into a small utility routine that could
>be part of Xmu or in the source of your own program:

The standalone library is a good idea of course. In fact this is how 
I've been using this myself. I have a libXtrm.a that I link in to 
my programs before libXt. Unfortunately, (as you pointed out)  because 
your standalone function requires a display, it doesn't work quite 
as intended unless the library redefines some of the Intrinsics intialization
functions. By the time you have opened the display, 
Xt has already loaded the user's resource files. Now you are in the 
position of overriding the users choices, not specifying defaults, which
is exactly what I was trying to avoid with my version. I tried to see
how this could be implemented to provide the needed functionality, without
depending on patches to the Intrinsics, but couldn't find a way. If you
like this capability, I think the best approach is to lobby for its inclusion
at some point (R5?).

Doug Young