Modsak Manual v3.16 - 1.5. Saving and restoring the configuration
Modsak's configuration can be saved to a disk file by selecting the register and command definitions) is saved to the file in an XML format.
→ menu item. This displays a dialog that enables you to enter or select the name of the file to save the configuration to. All of Modsak's configuration (includingTo restore the configuration from a file, use the
→ menu item. This displays a dialog that enables you to enter or select the name of the file to restore the configuration from. If Modsak is "running" (i.e. the button is depressed), you will have to click the button before you can load the configuration.Loading the configuration from a file will add new register definitions and replace existing register definitions, but will not delete any register definitions. If you want to totally replace the the set of register definitions you should delete all the register definitions (using the Delete All buttons in the Register Table and File Register Table pages) before loading the new configuration.
Similarly, loading the configuration will add new command definitions and replace existing command definitions, but will not delete any command definitions. If you want to totally replace the the set of register definitions you should delete all the command definitions (using the Delete All button in the Command Table page) before loading the new configuration.
You can also load the configuration from a file when you start Modsak, by passing the name of the file as a command-line argument, e.g.:
java -jar modsak3.16.jar config.xml
If you pass a folder/directory name on the command line instead of a file name, it will be used to set the current directory of the Load Configuration dialog.
There is, currently, no formal DTD (Document Type Definition) or XML schema for the format of the XML files in which the configuration is saved. However, the format should be fairly evident to a human reader, and can easily be edited, if necessary, using a text editor.