08c5cb671d
The concept of a disabled contextual item is nonsensical; the set of context-sensitive actions is always supposed to be responsive to the context. Accordingly, if the calling code has marked any actions as disabled, let's hide them entirely. We can't remove them from the model because they might become re-enabled at a time when the calling app sees fit (perhaps the context has changed). So instead we have to set visible to false and height to 0, to ensure that the listview has the correct height. This is a hack, but I don't see a better way to do it. The memory penalty to having invisible but created items should be negligible since there are only ever a maximum of about 3 items in here.
Plasma Framework
Foundational libraries, components, and tools of the Plasma workspaces
Introduction
The plasma framework provides the following:
- QML components
- A C++ library: libplasma
- Script engines
QML components
org.kde.plasma.core
Bindings for libplasma functionality, such as DataEngine and FrameSvg, see @ref core.
org.kde.plasma.components
Graphical components for common items such as buttons, lineedits, tabbars and so on. Compatible subset of the MeeGo components used on the N9, see @ref plasmacomponents.
org.kde.plasma.extras
Extra graphical components that extend org.kde.plasma.components but are not in the standard api, see @ref plasmaextracomponents.
org.kde.plasma.plasmoid
Attached properties for manipulating the current applet or containment, see @ref libplasmaquick
libplasma
This C++ library provides:
- rendering of SVG themes
- loading of files from a certain filesystem structure: packages
- data access through data engines
- loading of the plugin structure of the workspace: containments and applets
See @ref libplasma.
Script engines
Provides support to create applets or containments in various scripting languages.