On Sat, Aug 16, 2014 at 12:11:28PM +0100, Jamie Griffin wrote: > > On 16/08/2014 10:30, Dominik Vogt wrote: > >On Sat, Aug 16, 2014 at 09:50:15AM +0100, Jamie Griffin wrote: > >>Aside from any errors, would you have any recommendations to improve > >>what i'm trying to achieve? > >In my eyes, this is a good approach. Well, in the CloseFooOpenBar > >function you might want to check whether Bar is already open and > >only start it if it's not. > > > > + I none (Bar) <command to start Bar> > > > >This way you can also call the function elsewhere without creating > >duplicate instances of the dock or panel, e.g. when you restart > >fvwm. > > > >>One idea I had was to have a form of some kind pop-up when I start > >>the fvwm session asking which, if any, panel/dock i'd like to start. > >This will probably annoy you very quickly. Just choose a default > >you want and start that during fvwm startup. If it's not what you > >want sometimes, just press the key to switch. > > Thanks again for your help and suggestions. I got it working by > swapping out Next with None in the wrapper function.
Oh, I meant you should an additional "None" in the inner function so that you can call the inner functions without the wrapper at startup. > One thing i've considered is, having changed my taskbar/panel/dock > if I want to keep that layout for next session could this be easily > integrated with the FvwmSaveDesk module? FvwmSaveDesk hasn't been maintained in decades, you should rather not use it. But you can easily do something like .fvwm2rc: Read $HOME/.fvwm/setup_dock_or_panel Then add addtofunc closedockopenpanel ... + i exec exec echo clodedockopenpanel > $HOME/.fvwm/setup_dock_or_panel And the other way round in the other function. But make sure that you don't use a file in a publicly writeable location because then someone else could put his own fvwm commands in there. Ciao Dominik ^_^ ^_^ -- Dominik Vogt
