Thomas Adam wrote: > On Wed, Aug 11, 2010 at 01:23:43PM +0200, Michael Großer wrote: >> clock at the bottom right corner of my screen >> using 3 instances of xclock to let it show >> me the day of the week (1st instance), the >> date (2nd instance) and the time (3rd instance). >> Fvwm is automatically positioning these >> instances for me using "Wait" and "Prev" >> and setting some styles. > > Wait and Prev? Hmm, see the following as to why this is not a good thing > anymore: > > http://fvwmwiki.xteddy.org/Tips/FVWMStartupProcedure/ >
Today, I revised my "0009_clock" config file: > #AddToFunc StartFunction > AddToFunc InitFunction > + I Schedule 100 Exec exec xclock -digital -update 1 -strftime "%A " > -geometry 200x34-102-0 > + I Schedule 200 Exec exec xclock -digital -update 1 -strftime "%d.%m.%Y" > -geometry 114x34-90-0 > + I Schedule 300 Exec exec xclock -digital -update 1 -strftime "%H:%M:%S > Uhr" -geometry 108x34-0-0 > > > > # The clock is supposed to get styles! > Style xclock Sticky, NoTitle, HandleWidth 0, StaysOnBottom No unstabilising Waits anymore. I use the "-geometry" option now to place the instances onto the right coordinates. And the Schedule command ensures that the clocks start in the right order (the "date" overlays the "day of week", the "time" overlays the "date" (and not the other ways around)). Thanks for the hints. Now it's time to tweak these little details. Michael P.S. If there were an approach to save these additional 200 or 300 milliseconds to get the clocks into the right order (without having to risk FVWM to hang using the "Wait" command), I would be glad about this.
