On Sat, Jul 20, 2002 at 03:57:28AM +0000, Mikhael Goikhman wrote: > On 19 Jul 2002 18:02:35 +0200, Dominik Vogt wrote: > > > > > 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). > > > > 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. > > Well, for most of configurations when windows and modules are started in > StartFunction or InitFunction, the colorset commands may be anywhere in > the config file, even at the end. This is the whole point of these init > functions, they are started after the whole initial configuration is read. > > And it is not critical if a colorset is defined (or changed) after some > color is already used. There will be a redraw at most. This is the whole > point of dynamically changeable colorsets. :) > > The order of colorset commands can't be a reason for the original problem.
Yes, you're probably right. Anyway, it's still a very good idea to define your colour sets before anything else. There can be a large number of unnecessary redraws if you define color sets last. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- 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 [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
