On 22 May 2003 08:44:47 +0200, Fabio Stumbo wrote: > > > > Now I use 2 desktops. I realized that my scripts have the effect to put > > > the same image in the two desktop. What I want now is: on the first > > > desktop (=0), same behavior as before. On the second desktop (=1), I > > > would like to have a solid color background, which shouldn't change. I > > > made some tries with FvwmBacker, but without success, so I am out of > > > ideas: can anybody help me? > > > > You may run FvwmBacker that uses 2 Pixmap colorsets, one per desk. > > Then the setup for 2.5.x may look like this (untested): > > > > DestroyFunc ChangeRootHourly > > AddToFunc ChangeRootHourly > > + I PipeRead `dump-2-config-lines-for-colorset-51-and-52` > > + I Schedule 3600000 ChangeRootHourly > > > > AddToFunction StartFunction > > + I ChangeRootHourly > > + I FvwmBacker > > > > *FvwmBacker: Command (Desk 0) Colorset 51 > > *FvwmBacker: Command (Desk 1) Colorset 52 > > > > The script should dump 2 lines, something like: > > > > Colorset 51 Pixmap bg7.png > > Colorset 52 Pixmap bg4.png > > I tried: your suggestion works fine. Only two point: > > 1) am I forced to use png? I have lots of jpgs, so I should convert them. > Ok, it is simple and quick, but it is somewhat a waste of space to have > two copies of hundreds of pictures...
I would also like FVWM to support JPG together with PNG, XPM and XBM, but I am afraid this is not going to happen until at least 2.7.x. > 2) Your suggestion has the effect that the background gets changed every > hour _since_ I fire up fvwm: what if I want the effect only exactly at the > hour (3:00, 4:00, 5:00, and so on...)? Well, then you should do some time mathematics. Replace the "Schedule 3600000 ChangeRootHourly" line above with: PipeRead `perl -MTime::Local -e '@t = localtime; $t[0] = $t[1] = 0; $t[2]++; printf "Schedule %s ChangeRootHourly\\n", ((timelocal @t) - time) * 1000'` Regards, Mikhael. -- 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]