rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (11/14/88)
Take a look at the xrdb man page; xrdb allows you to make use of the C preprocessor to load attribute-dependent resources onto the server.
janssen@TITAN.SW.MCC.COM (Bill Janssen) (11/15/88)
\begindata{text, 1697076}
\textdsversion{12}
\template{messages}
\bold{xrdb} is nice, but it's still based on the model of one screen per server, and
doesn't tell me what the screen resolution is (though yes, I can guess, given
the size in pixels). I think you've licked the X10 problem of multiple
\typewriter{.Xdefaults} files for different servers, but now have the
(unlicked) problem of how to specify the parameters for different quality
screens on the same server.
Bill\
\enddata{text,1697076}rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (11/15/88)
\bold{xrdb} is nice, but it's still based on the model of one screen per
server, and doesn't tell me what the screen resolution is (though yes, I
can guess, given the size in pixels).
Via the C preprocessor, xrdb provides resolution information:
X_RESOLUTION=num
the x resolution of the screen in pixels per meter.
Y_RESOLUTION=num
the y resolution of the screen in pixels per meter.
I think you've licked the X10 problem of multiple .Xdefaults files
for different servers, but now have the (unlicked) problem of how to
specify the parameters for different quality screens on the same server.
Right. We realize that (but I didn't hear that particular complaint
in your original message, sorry).