[comp.windows.x.motif] Different decoration colors for specified clients?

pjs@euclid.jpl.nasa.gov (Peter Scott) (10/15/90)

Hi.  I'd like to be able to change the decoration colors
(fg, bg, and if possible, the same when active) for windows
on a client-by-client basis.  I thought I might be able to
do that by putting an -xrm "Mwm*client*background:puce" option
on the client invocation command line, but it didn't work.
Neither have several attempts in the .Xdefaults file.  Can this
be done?  Using 1.0.a w/X11R4.18 at the moment.


-- 
This is news.  This is your       |    Peter Scott, NASA/JPL/Caltech
brain on news.  Any questions?    |    (pjs@aristotle.jpl.nasa.gov)

keith@hpcvlx.cv.hp.com (Keith Taylor) (10/20/90)

>I'd like to be able to change the decoration colors
>(fg, bg, and if possible, the same when active) for windows
>on a client-by-client basis.  

You can't do this. The colors on the frames are restricted (for
usability reasons) to one set for active and another for inactive.
This way, you can easily see the window with the keyboard focus
at a glance.


Keith M. Taylor		keith@cv.hp.com	
Hewlett-Packard
Corvallis, Oregon

dce@smsc.sony.com (David Elliott) (10/22/90)

In article <110630021@hpcvlx.cv.hp.com> keith@hpcvlx.cv.hp.com (Keith Taylor) writes:
>>I'd like to be able to change the decoration colors
>>(fg, bg, and if possible, the same when active) for windows
>>on a client-by-client basis.  
>
>You can't do this. The colors on the frames are restricted (for
>usability reasons) to one set for active and another for inactive.
>This way, you can easily see the window with the keyboard focus
>at a glance.

On the one hand, I see your point.  It should be fairly obvious to
the user which window has focus, and color is the way it is done
for mwm.

On the other hand, it's unreasonable to say "Why would anyone want to
do that?" if you want people to use your product.  I switched to tvtwm
for the virtual root, and decided I liked the configurability.  I can
have all of my local xterms have one color titles and borders, my
remote xterms with another, and my other clients with another color.

It seems to me that you are saying "it's to prevent users from
shooting themselves in the foot".  Yet the user can remove borders,
functions, and buttons from specified clients, which can cause just
as many problems (mwm doesn't provide the ability to choose
functions from the root window and have this allow the user to
choose the window by clicking on it -- another twm feature that
would be useful).

I see the fact that you can set client border colors as simply
an omission, not a protection.  Mwm's lack of configuration in
some areas is a weakness for more advanced users.