> The only problem could be if NoCharge means "Unknown", but I assume that's
> academic.
NoCharge as far as Solid Battery is concerned means either "not charging",
"not yet charging" (eg. just plugged in AC), "not yet discharging" ("pending
discharge"), or "unknown". It does know "fully charged"
On Sonntag, 17. Mai 2015 21:32:55 CEST, Kai Uwe Broulik wrote:
Sorry for the inconvenience,
No problem. As Thiago confirmed, iterating over all batteries to check if any
is discharging actually is sufficient (if there's no battery or none
discharging we're either on AC, just nuked #1 Thermo
Hi Thomas,
I'm afraid there is no replacement currently, the overall situation is a bit
of a mess. Lukas Tinkl is currently working on a proper replacement for the
Solid::PowerManagement stuff, called solid-power, which will have the
appShouldConserveResources thingie like the old one. PowerDev
On Sunday 17 May 2015 11:39:46 Thomas Lübking wrote:
> Solid::AcAdapter was removed from the API and I don't see a replacement.
> Does that mean one only has to care about Solid::Battery in KF5?
>
> And if: how do I know the System is on AC?
> Battery::chargeState() != Battery::Discharging?
That'
Solid::AcAdapter was removed from the API and I don't see a replacement.
Does that mean one only has to care about Solid::Battery in KF5?
And if: how do I know the System is on AC?
Battery::chargeState() != Battery::Discharging?
Thanks,
Thomas
Visit http://mail.kde.org/mailman/listinfo/kde-dev
