Or even load previous file(s)!
Full Version: "Save Current Config"&"Load Previous Conf" But
It will help us to save ourself's CFG file easily,when we need to change our current config and want it back later.
Or even load previous file(s)!
Or even load previous file(s)!
Well, I'm guessing you want to save the config as in all of foobar's settings. If you're referring to formatting strings you should check out my foo_syfm plugin, but enough of that fairly shameless plug.
As far as backing up the main configuration file, the backing up part would be easy - just write a plugin that makes a copy of the file. Of course, since foobar only writes to the file on exit you'd have to restart first to get it to be up to date. As for restoring a backup, that would be rather difficult - since foobar writes to the file on exit, reads from it on load, and ignores it at all other times, you'd need the assistance of another program to copy the backup *after* foobar is done writing the current file, and *before* it loads the file from disk when you run it again. Which is impossible with plugins. So I'm afraid the only solution at the moment is to use explorer to copy the file and then restore it later.
As far as backing up the main configuration file, the backing up part would be easy - just write a plugin that makes a copy of the file. Of course, since foobar only writes to the file on exit you'd have to restart first to get it to be up to date. As for restoring a backup, that would be rather difficult - since foobar writes to the file on exit, reads from it on load, and ignores it at all other times, you'd need the assistance of another program to copy the backup *after* foobar is done writing the current file, and *before* it loads the file from disk when you run it again. Which is impossible with plugins. So I'm afraid the only solution at the moment is to use explorer to copy the file and then restore it later.
QUOTE(billcow @ Dec 21 2003, 11:08 PM)
you'd need the assistance of another program to copy the backup *after* foobar is done writing the current file, and *before* it loads the file from disk when you run it again. Which is impossible with plugins.
Well, a plugin could do this, it just has to wait until foobar is finished shutting down, copy the config and start foobar again. So how does a plugin manage to stay active in some form, when foobar is quitting? rundll32.exe
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.