Commit 6b27bcef authored by Leena Miettinen's avatar Leena Miettinen
Browse files

Doc: enabling and disabling plugin dependencies

This now happens automatically and disabled plugins
are no longer a problem after version upgrade even if
plugin dependencies have changed.

Change-Id: I06456c81c2ad2fab5730562a4df407cf178fd1cf
Reviewed-by: default avatarEike Ziller <>
parent 549590a2
......@@ -108,11 +108,22 @@
\li -load <plugin>
\li Load the specified plugin.
\li Enable the specified plugin and all plugins that it depends on.
You can combine \c -load and \c -noload options and specify both
options multiple times to enable and disable several plugins.
The actions are executed in the specified order.
\li -load all
\li Enables all plugins.
\li -noload <plugin>
\li Do not load the specified plugin.
\li Disable the specified plugin and all plugins that depend on it.
\li -noload all
\li Disables all plugins.
\li -profile
......@@ -158,13 +158,11 @@
New \QC plugins are often introduced as \e {experimental plugins} to let
you try them out before they are fully supported. Experimental plugins
are disabled by default and you must enable them for them to become visible
after you restart \QC.
after you restart \QC. By default, all the plugins that the plugin depends
on are also enabled.
You can also disable plugins that you do not use, to streamline \QC.
However, this might cause problems when using another plugin later if the
dependencies between plugins are changed between \QC versions. Once you
manually disable a plugin, it stays disabled even when you upgrade to a
new \QC version, and you must manually enable it to be able to use it.
By default, all the plugins that depend on the plugin are also disabled.
To enable and disable plugins, select \uicontrol Help > \uicontrol {About Plugins}.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment