Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!orca!mesa!rthomson
From: rthomson@mesa.dsd.es.com (Rich Thomson)
Newsgroups: comp.windows.x
Subject: Re: X.V11R4 resource inheritance hassles
Message-ID: <1991Jun24.221732.8062@dsd.es.com>
Date: 24 Jun 91 22:17:32 GMT
References: <9106210733.AA06821@lightning.McRCIM.McGill.EDU>
Sender: usenet@dsd.es.com
Reply-To: rthomson@dsd.es.com (Rich Thomson)
Organization: Design Systems Division, Evans & Sutherland, SLC, UT
Lines: 21
Nntp-Posting-Host: 130.187.85.21

In article <9106210733.AA06821@lightning.McRCIM.McGill.EDU>
	mouse@lightning.mcrcim.mcgill.EDU (der Mouse) writes:
>
>To my mind, an application should always look for resources first in
>the screen's resource database, and fall back on its internal defaults
>(the app-defaults file, the compiled-in defaults, whatever) only if it
>can't find what it wants in the resource database.  Anything else is a
>bug, that simple.  No?

Does one have this fine a level of control in an Xt based application?
The widgets look up their resources via XrmGetResource, but you don't
get to control which database the resource fetch is done on.  [Please
correct me if I'm wrong -- I'm not talking from the position of having
examined the Xt code, it just seems the most logical thing to do]

							-- Rich
-- 
  ``Read my MIPS -- no new VAXes!!'' -- George Bush after sniffing freon
	    Disclaimer: I speak for myself, except as noted.
UUCP: ...!uunet!dsd.es.com!rthomson		Rich Thomson
Internet: rthomson@dsd.es.com			PEXt Programmer