Mikhael Goikhman <[EMAIL PROTECTED]> writes: > One more idea, storing a final configuration after some script or module > sent dynamical changes to FvwmButtons. Something like: > > SendToModule FvwmButtons-Alias SaveConfig > > The config file name may default to $FVWM_USERDIR/FvwmButtons-Alias . > I.e. to invoke the initial configuration: > > Read FvwmButtons-Alias > FvwmButtons FvwmButtons-Alias > > The first line may be even redudant, i.e. the second one may do it > automatically just like FvwmForm does.
Having a module do an automatic read for its config seems like a reasonable thing. That would let a user read in pre-packaged module configurations. For FvwmButtons, FvwmForm, etc. the saving of the config should probably be done by a future GUI that lets you design the buttonbar or form. -- Dan Espen E-mail: [EMAIL PROTECTED] 444 Hoes Lane Room RRC 1C-214 Phone: (732) 699-5570 Piscataway, NJ 08854 -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
