16.3. How to Save Settings¶
To save preferences in VisIt, select Save settings from the Main window’s Options menu. When VisIt saves the current settings to the users preferences file they are used to set the initial state the next time the user runs VisIt. VisIt does not automatically save settings when changes are made to the default attributes for plots, operators, or various control windows. For windows that only have current attributes (windows without a Make default button), the current attributes are saved. For windows that have current and default attributes (windows with a Make default button), the default attributes are saved.
To save the entire state of VisIt, which includes things such as the plots in the window and the operators applied to the plots for each visualization window, select either Save session or Save session as from the Main window’s File menu. When using Save session, if a session has already been restored or saved, VisIt will overwrite the existing session file. If a session has not already been restored or saved, VisIt will bring up a dialog window that will allow the user to specify the location and name of the session file. When using Save session as VisIt will always bring up a dialog window that will allow the user to specify the location and name of the session file and prompt the user to confirm before overwriting an existing session file.
VisIt saves two preference files, the first of which stores preferences
for VisIt’s GUI while the second file stores preferences for VisIt’s
state. When running VisIt on UNIX and MacOS X systems, the preference files
config and they are saved in the
directory in the users home directory. The Windows version of the
%USERPROFILE%\Documents\VisIt, which may be something like:
To run VisIt without reading the saved settings, add
-noconfig to the
command line when running VisIt. The
-noconfig argument is often
useful when running an updated version of VisIt that is incompatible with
the saved settings. VisIt settings are usually compatible between different
versions but this is not always the case and some users have had trouble
on occasion when transitioning to a newer version. If VisIt has stability
problems when it starts up after upgrading to a newer version, add the
-noconfig option to the command line and save the settings to write over
any older preference files.