Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!think!prometheus.think.com!garyo
From: garyo@prometheus.think.com (Gary Oberbrunner)
Newsgroups: comp.windows.x
Subject: Xrdb loads the root window OF SCREEN 0???
Message-ID: <30075@news.Think.COM>
Date: 26 Sep 89 02:43:27 GMT
Sender: news@Think.COM
Lines: 32

Somehow it just dawned on me (after all this time) that the
XA_RESOURCE_MANAGER property is always stored on and fetched from the root
window OF SCREEN 0, even if you say 'xrdb -display :0.1 ~/.Xrdb' or open
display :0.1.

Of course this is certainly NOT what one would want, since I have a color
Sun 4 with two virtual screens, one color and one black & white.  If I use

#if COLOR
... color stuff ...
#else
... b/w stuff ...
#endif

I get a very bad result on one or the other screen, depending on which
screen I run the xrdb on.  Xrdb DOES pay attention to the screen number
when it opens the display; it just ignores it when storing the property.
And similarly XOpenDisplay sets dpy->xdefaults with the call
XGetWindowProperty(dpy, RootWindow(dpy, 0), ...)

Why is this?  Is it being fixed in R4?  Should I send in a bug report?  How
on earth could it have taken me so long to discover this?  I found it while
trying to bring up mwm on both screens; I had to rerun xrdb each time I
restarted mwm on that screen.  Oh well, I guess for now I'll just have to
run gwm, which doesn't depend on the xdefaults mechanism to get its colors
and pixmaps - they're specified in the .gwmrc file and can easily be
conditionalized for color vs. b/w.


					As always,

					Gary O