2008/7/31 Thomas Adam <[EMAIL PROTECTED]>: > 2008/7/31 Ethan Romander <[EMAIL PROTECTED]>: >> I'd like to start an application in the iconified state from within my >> FVWM InitFunction. I know that I can use the "Exec foo" command to > > No -- you want to associate it in your StartFunction testing for Test (Init). > >> My best guess looks like this: >> >> Style foo StartIconic >> Exec foo >> Wait foo >> Style foo StartNormal > > Which is all you can do yes. Since you predicate the fact that any > instances of foo running before you exec a *specific instance* of foo, > you have no choice but to do: > > AddToFunc StartFunction > + I Test (init) SomeFoo > > DestroyFunc SomeFoo > AddToFunc SomeFoo > + I Exec exec foo -iconic > + I Wait foo > + I Style foo StartNormal
This is incorrect of me - having realised what you meant. Your example mislead me. # Default case -- if you want foo iconic, damn well tell it to. If "foo" accepts a way to change a class/title use it to your # advantage in its style. Style foo StartNormal # Now your function DestroyFunc SomeFoo AddToFunc SomeFoo + I Exec exec foo -iconic + I Wait foo If this "foo" application doesn't have an iconify flag to it then: DestroyFunc SomeFoo AddToFunc SomeFoo + I Exec exec foo + I Wait foo + I Next (foo) Iconify Which is more likely in your case -- really, StartIconic is only useful on brain-dead applications which don't provide an -iconic flag, I will ask though why this is such a special case on *init*. The only usecase for this is if you start up "foo" specifically before FVWM starts up --- but this seems odd. Very odd. So how can there be more copies of foo running *prior* to the SomeFoo function running at Init? Either way, suggest you clarify. I hope this helps. -- Thomas Adam
