grady@fxgrp.fx.com (Steven Grady) (01/06/90)
I hereby register a complaint about the new default background color for the xterm pointer. It used to be the color of the background of the window. Now it's XtDefaultBackground. Since I liked it the old way, and since I like to have different window backgrounds for different machines, I have to specifically set the pointer background color along with the color for every different machine I use. Use the Background class, I hear you say? Well, since I'm setting my background with the XENVIRONMENT variable, using the Background class is too general, since it gets used by every application, not just xterm. (In case anyone's interested, Motif uses the Background class for each of its dynamically-configured colors that are used for nifty shading. So if you specify the Background class, you don't get the 3-D shading any more.) [time passes...] Well, I found a way to do what I want (although I didn't even get into other complexities such as describing my scripts to insert appropriate Color definitions in my .twmrc, given a list of XENVIRONMENT files), but still, the new default is annoying. I have no problem with adding new configurable parameters, but the default should have remained the same. If someone wants a specific color (such as white [== XtDefaultBackground]), they can set it themselves with one resource entry. But if you want to pointer color to be the same as the window background, that's a lot harder. -- Steven ...!ucbvax!grady grady@postgres.berkeley.edu "I may be synthetic, but I'm not stupid."