Unset: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(2.5 updates) |
||
(4 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
'''unset''' behaves in two ways. | |||
If selection is not provided: | |||
* Since PyMOL 2.5: Changes the named global setting to the default value. | |||
* Before PyMOL 2.5: Changes the named global setting to a zero or off value. | |||
If a selection is provided, then "unset" undefines object-specific or state-specific settings so that the global setting will be in effect. | |||
== Usage == | |||
unset name [,selection [,state ]] | |||
== Python API == | |||
== | |||
<source lang="python"> | |||
cmd.unset ( string name, string selection = '', | |||
int state=0, int updates=1, int log=0 ) | |||
== | </source> | ||
== See Also == | |||
* [[unset_deep]] | |||
* [[set]] | |||
[[Category:Commands| | [[Category:Commands|Unset]] | ||
[[Category:States]] |
Latest revision as of 04:55, 29 January 2021
unset behaves in two ways.
If selection is not provided:
- Since PyMOL 2.5: Changes the named global setting to the default value.
- Before PyMOL 2.5: Changes the named global setting to a zero or off value.
If a selection is provided, then "unset" undefines object-specific or state-specific settings so that the global setting will be in effect.
Usage
unset name [,selection [,state ]]
Python API
cmd.unset ( string name, string selection = '',
int state=0, int updates=1, int log=0 )