Difference between revisions of "Documentation/Nightly/SlicerApplication/ApplicationSettings"
(→Panels) |
|||
Line 57: | Line 57: | ||
| | | | ||
|valign="top"|[[Image:PythonSettings.png|thumb|400px|Python settings panel]] | |valign="top"|[[Image:PythonSettings.png|thumb|400px|Python settings panel]] | ||
+ | |} | ||
+ | ==Units== | ||
+ | {| | ||
+ | | | ||
+ | |valign="top"|[[Image:UnitsSettings.png|thumb|400px|Units panel]] | ||
|} | |} | ||
==Volume Rendering== | ==Volume Rendering== | ||
Line 65: | Line 70: | ||
== Others == | == Others == | ||
Extensions can also add their own settings panel. | Extensions can also add their own settings panel. | ||
+ | |||
= Information for Advanced Users = | = Information for Advanced Users = | ||
Settings are stored in an *.ini file located: | Settings are stored in an *.ini file located: |
Revision as of 22:27, 29 May 2013
Home < Documentation < Nightly < SlicerApplication < ApplicationSettingsContents
Panels
General
Modules
Skip Loading ofSelect which 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 Prefer Executable CLIsUse 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. 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 directoryDirectory where modules can store their temporary outputs if needed. Additional module pathsList 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. ModulesList 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:
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. HomeModule that is shown when Slicer starts up. FavoritesList of modules that appear in the 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. |
Extensions
Cache
Python
Units
Volume Rendering
Others
Extensions can also add their own settings panel.
Information for Advanced Users
Settings are stored in an *.ini file located:
- Windows: C:\Users\USERNAME\AppData\Roaming\NA-MIC\Slicer.ini
- Linux: ~/.config/NA-MIC/Slicer.ini
- Mac: ~/.config/www.na-mic.org/Slicer.ini
Deleting the file restores all the settings to default.