Alas! Mikhael Goikhman spake thus: > > not sure if the '-T' is necisito. > > Yes, it is necessary to distinguish them, because Rob wants to grow xterms > in the certain order if I understand. -n is stronger, -name is even more. > > When Wait above is passed it is not guaranteed that 4 xterms are already > up, it is only guaranteed that only one xterm4 is up. And if you group all > four Wait together it may hang from time to time. This works (note -g): > > DestroyFunc Xterm4CreateGrow > AddToFunc Xterm4CreateGrow > + I Exec exec xterm -n xterm1 -g +0+0 > + I Wait xterm1 > + I Exec exec xterm -n xterm2 -g -0+0 > + I Wait xterm2 > + I Exec exec xterm -n xterm3 -g +0-0 > + I Wait xterm3 > + I Exec exec xterm -n xterm4 -g -0-0 > + I Wait xterm4 > + I Next (xterm1) Maximize grow grow > + I Next (xterm2) Maximize grow grow > + I Next (xterm3) Maximize grow grow > + I Next (xterm4) Maximize grow grow
Ok, you've almost got it! ;) This works, except that the second (or later) time I run it, whichever xterm had the mousecursor over it doesn't get grown, and an xterm with the same name on another desk gets ungrown. The ungrown thing could be avoided with "Maximize true grow grow", but it doesn't change the fact that the current window is not grown. Mostly this just leads to odd results like this: +---------+--------------+ |xterm |xterm | | | | | | | +---------+ | |xterm | | | | | | | | | +--------------+ | |xterm | | | | | | | +---------+--------------+ But it's still maximum utilized screen space, so I'm not really complaining ;) Thanks. -- Rob 'Feztaa' Park http://members.shaw.ca/feztaa/ -- We come to bury DOS, not to praise it. (Paul Vojta, [EMAIL PROTECTED], paraphrasing a quote of Shakespeare) -- 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]
