Sets the profiles via the wrapped ui in powerdevil if available.
If the performance profile is inhibited, the second half of the slider
will look disabled and it will be impossible to move it to performance.
Co-authored-by: Kai Uwe Broulik <kde@privat.broulik.de>
This adds a new "Inhibitions" source which has keys for each application
(amarok, vlc, ...) and inside a QVariantMap with the pretty application name
(taken from the desktop file through KService and cached localle), the
application icon and the reason for the inhibition (as provided by the app)
REVIEW: 122132
in case of several batteries; a plain "sum/count" won't do it,
especially when the batteries have different Energy. Take that into
account, report it thru the dataengine and do the math correctly
This should eventually allow us to react to hotplugging a keyboard and provide brightness
controls then. It does not yet watch for PowerDevil's availability on DBus (eg. when kded
takes a bit longer to startup), and also PowerDevil's brightness controls don't support
on-demand activation yet
REVIEW: 121365
Now that we can finally use absolute brightness values, rather than a fixed 0 - 100% range,
those values should be exposed in the dataengine. This allows us to eg. properly handle
keyboard brightness controls which usually have just a few steps
Also clean up code by moving stuff into lambdas and reworking the ugly brightness availability stuff.
REVIEW: 121355
This patch adjusts the Plasma powermanagement (and soliddevice) dataengine to use the renamed isPresent() method instead of isPlugged().
It does not rename the exposed property "Plugged in" to not break its users.
REVIEW: 118558
This is the beginning of revision history for this module. If you
want to look at revision history older than this, please refer to the
techbase wiki for how to use Git history grafting. At the time of
writing, this wiki is located here:
http://community.kde.org/Frameworks/GitOldHistory
If you have already performed the grafting and you don't see any
history beyond this commit, try running "git log" with the "--follow"
argument.
Branched from the monolithic repo kde-workspace, frameworks branch, at commit
049113e719dd2fc4446d054fa1a3aada330094f0