mayer.WBST128@XEROX.COM (04/11/89)
Why is XA_RESOURCE_MANAGER always taken off the root window of screen 0? This seems like a mistake to me. In particular, it makes it difficult to customize properties (such as default fonts, colors, etc.) to screens of differing capabilities. We've run into this problem here because many of our workstations have both color (80 or 100 dpi) and monochrome (115 dpi) screens. I suggest that either of the two following conventions would be superior: (1) XOpenDisplay looks first on the window returned by DefaultRootWindow(). If no XA_RESOURCE_MANAGER property is found, it then looks at RootWindow(dpy, 0). (2) XOpenDisplay works as currently defined, however the resource manager is changed to first load the standard X defaults, and then load a screen specific set of X defaults (either XA_RESOURCE_MANAGER on another screen, or something like XA_SCREEN_SPECIFIC_RESOURCES). If this hasn't been discussed before, I will volunteer to file an "official" bug report. -- Jim Mayer Member Research Staff Systems Sciences Laboratory Xerox Webster Research Center 800 Phillips Road, 0128-29E Webster, New York 14580 Phone: (716) 422-9407 EMail: mayer.wbst128@xerox.com (James L Mayer:wbst128:Xerox)