Enable: Difference between revisions
Jump to navigation
Jump to search
Jaredsampson (talk | contribs) (Added more examples and description of `parents` argument.) |
|||
| Line 1: | Line 1: | ||
The '''enable''' command toggles on the display of all currently visible representations of an object. It is the equivalent of selecting the object in the list at the top of the [[Internal_gui|Internal GUI]]. | |||
===USAGE=== | |||
enable [name [, parents]] | |||
When run with no arguments, all loaded objects are enabled. | |||
= | Running it with parents=1 will enable the named object and all parent objects of the named object (recursively), so that it won't be hidden by having a parent object (or [[group]]) that is [[disable|disabled]]. | ||
===PYMOL API=== | ===PYMOL API=== | ||
<source lang="python"> | <source lang="python"> | ||
cmd.enable( string | cmd.enable( string name='all', int parents=0 ) | ||
</source> | </source> | ||
=== | ===EXAMPLES=== | ||
enable my_object | enable my_object | ||
enable (my_object1 or my_object2) | |||
enable my_object* | |||
enable | |||
enable my_object, parents=1 | enable my_object, parents=1 | ||
Revision as of 17:42, 11 April 2014
The enable command toggles on the display of all currently visible representations of an object. It is the equivalent of selecting the object in the list at the top of the Internal GUI.
USAGE
enable [name [, parents]]
When run with no arguments, all loaded objects are enabled.
Running it with parents=1 will enable the named object and all parent objects of the named object (recursively), so that it won't be hidden by having a parent object (or group) that is disabled.
PYMOL API
cmd.enable( string name='all', int parents=0 )
EXAMPLES
enable my_object enable (my_object1 or my_object2) enable my_object* enable enable my_object, parents=1