Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!spool2.mu.edu!uunet!mcsun!cernvax!chx400!ugun2b!ugun2a!paccini
From: paccini@uni2a.unige.ch
Newsgroups: comp.windows.open-look
Subject: Re:  OpenWindows backgrounds (dammit)
Message-ID: <1991Jan22.110637.824@uni2a.unige.ch>
Date: 22 Jan 91 09:06:37 GMT
References: <4w5wjtp@openlook.Unify.Com>
Organization: University of Geneva, Switzerland
Lines: 34

In article <4w5wjtp@openlook.Unify.Com>, grp@magpie.unify.com (Greg Pasquariello) writes:

[...]
>>
>>Is there something that I'm just too blind to see, or is this thing really
>>designed so bass-ackwards that you can't customize your background 
>>automatically (unless of course you like solid "colors")?
[...]
> 
> Whats happening is a race condition between the olwm and
> the xsetroot.  I am unaware of any resources that will allow you
> to do this kind of thing,

If you look at the "olwm" man page, you can see an interesting ressource
whose name is "Workspacecolor":
     WorkspaceColor (color specification)
           Specify the color  for  the workspace  (root  window).
           This  may  be  a color name, an RGB specification (pre-
           ceded by a `#'), an absolute pathname specifying an  X
           bitmap file, or a null value.  If any non-null value is
           specified, olwm will set the root window to that  color
           or pattern on startup and restore the system default on
>>>        shutdown.  If a null value is specified, olwm will  not
>>>        change  the  root background at all.  This is useful if
>>>        you prefer to use programs  that  set  the  root back-
>>>        ground, such as xsetroot(1).  Default value: #40a0c0. 

I use it, and it works fine.

-------------------------------------------------------------------------------
Jean-Francois Paccini			| paccini@cuisun.unige.ch
CUI					| paccini@cgeuge51.bitnet
University of Geneva			| mcsun!chx400!cui!paccini   	
Switzerland				|