On Fri, Jul 19, 2002 at 05:29:19PM +0200, Marcus Lundblad wrote:
> I have a script that outputs a current colour set.
> For example the outpu looks like this:
> Colorset 0 bg rgb:60/a0/a0, fg rgb:ff/ff/ff
> Colorset 1 bg rgb:d3/d3/d3, fg rgb:00/00/00
>
> further I have defined:
>
> Style * ActiveColorset 0
> Style * Colorset 1
>
> That script is run using PipeRead during start. But get all window borders
> white with black text (I think black on white is default for unitialised
> colour sets).
> But if I paste these lines (from the output) manually into an FvwmConsole,
> it works.
> But if I run my function SetColors, which is run from init in the
> FvwmConsole I get only white and black like above.
>
> Does it have to do with PipeRead?
>
> Any idea of what's wrong?
The colorset commands should be the first commands in your config
file. For performance reasons, colorset updates are ignored
during startup when a lot of things happen. This is probably the
reason for your problem.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, mail: dominik.vogt_at_schlund.de, phone: 0721/91374-382
Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Fri Jul 19 2002 - 11:03:59 BST