View source for Documentation/4.2/SlicerApplication/ApplicationSettings

<noinclude>{{documentation/versioncheck}}</noinclude>
=General=
{|
|
|valign="top"|[[Image:GeneralSettings.png|thumb|400px|General settings panel]]
|}
=Modules=
{|
|
===Skip Loading of===
Select which [[Documentation/{{documentation/version}}/Developers/Modules|type of modules]] to not load at startup. It is also possible to start slicer by temporarily disabling those modules (not saved in settings) by passing the arguments in the command line.

For example <code>$ .\Slicer.exe --disable-cli-modules</code> will start Slicer without any CLI loaded.

===Prefer Executable CLIs===
Use the executable version of a CLI instead of its shared version. CLI modules typically come in 2 forms, as shared (dll)and as executable (exe). By default, if there is a shared version, it is the one loaded by Slicer, ignoring the executable version. Loading a shared runs the module faster but increases the memory consumption. For some configurations (e.g. Windows 32b), memory is critical. Toggling this option to ON skips the loading of shared CLIs and loads executable version of CLIs instead. If there is no executable for a given CLI, the shared version is used.

===Show hidden modules===
Some modules don't have a user interface, they are hidden from the module's list. For debugging purpose, it is possible to force their display

===Temporary directory===
Directory where modules can store their temporary outputs if needed.

===Additional module paths===
List of directories scanned at startup to load additional modules. Any CLI, Loadable or scripted modules located in these paths will be loaded. Extensions are listed in the list, to remove an extension, use the Extension Manager instead.

===Modules===
List of modules loaded, ignored or failed to load in Slicer. An unchecked checkbox indicates that module should not be loaded (ignored) next time Slicer starts. A text color code is used to describe the state of each module:
** Black: module successfully loaded in Slicer
** Gray: module not loaded because it has been ignored (unchecked)
** Red: module failed to load. There are multiple reasons why a module can fail to load. Look at startup [[Documentation/{{documentation/version}}/SlicerApplication/ErrorLog|log outputs]] to have more informations.
If a module is not loaded in Slicer (ignored or failed), all dependent modules won't be loaded. You can verify the dependencies of a module in the tooltip of the module.

You can filter the list of modules by untoggling in the advanced (>>) panel the "To Load", "To Ignore", "Loaded", "Ignored" and "Failed" buttons.

===Home===
Module that is shown when Slicer starts up.

===Favorites===
List of modules that appear in the Favorites toolbar.
[[Image:FavoritesToolbar.png|Favorites toolbar]]
To add a module, drag&drop it from the ''Modules'' list above. Then use the advanced panel (>>) to reorganize/delete the modules within the toolbar.
|valign="top"|[[Image:ModulesSettings.png|thumb|400px|Modules settings panel]]
|}
=Extensions=
{|
|
|valign="top"|[[Image:ExtensionsSettings.png|thumb|400px|Extensions settings panel]]
|}
=Cache=
{|
|
|valign="top"|[[Image:CacheSettings.png|thumb|400px|Cache settings panel]]
|}
=Python=
{|
|
|valign="top"|[[Image:PythonSettings.png|thumb|400px|Python settings panel]]
|}
=Volume Rendering=
{|
|
|valign="top"|[[Image:VolumeRenderingSettings.png|thumb|400px|Volume Rendering settings panel]]
|}