Darren Upsolla wrote:
From: des...@verizon.net
Date: Wed, 16 Sep 2009 20:33:29 -0400
Generally you should use InitFunction to start applications:
DestroyFunc InitFunction
AddToFunc InitFunction
+ I Exec exec xsetroot -solid cyan
+ I Exec exec xterm
+ I Exec exec firefox
oh - but that post says:
"*INITFUNCTION IS CALLED ONCE -- AT INIT TIME WHEN FVWM FIRST STARTS.
STARTFUNCTION IS CALLED AT INIT AND RESTART.*
So you can see now that you only need one function for your purposes,
as you can add checks to StartFunction to tell it to do one thing if
FVWM is initialising, and another if it's not (i.e., presumably at
restart)."
maybe thats why i am confused lol! why is this not in the manpage then?
Yes InitFunction, StartFunction, RestartFunction were the older way of
doing it. Now due to Test () this can all be done in a single function
StartFunction. I think it makes things a bit easier to locate and keep
track of. I am unsure if the InitFunction and RestartFunction will be
depreciated in the future. The trend I see is to use only a
StartFunction and Test ().
This is in the man page:
You do not need to define all special functions if some are empty.
Also note, all these special functions may be emulated now using
StartFunction and ExitFunction, like this:
DestroyFunc StartFunction
AddToFunc StartFunction
+ I Test (Init) Module FvwmBanner
+ I Module FvwmPager * *
+ I Test (Restart) Beep
DestroyFunc ExitFunction
AddToFunc ExitFunction
+ I Test (Quit) Echo Bye-bye
+ I KillModule MyBuggyModule
+ I Test (ToRestart) Beep
jaimos
