it was from the time it wasn't possible to configure applets otherwise
now they can be configured with RMB as all the other applets
it introduced some confusing inconsistencies and clutter
BUG:336212
I am really tired of this topic. Yes, the battery remaining time is not that accurate and
jumps around (the latter is something that could be fixed using a moving average). But if
we jump onto that train we would also need to remove the battery percentage itself as it's not
accurate either. 30% on a dead battery can quickly become 5% and then the notebook suddenly
turns off. "Battery: Present".
The remaining time is in the battery's tooltip, many distributions have even patched the
battery monitor to show the time by default, there's even a clone of the original battery
monitor on GHNS just with that option enabled; every other desktop environment even emphasizes
the remaining time, Windows prefers the time over percentage, Mac OS X allows you to put
the remaining time in the panel rather than the percentage, etc etc.
As a maintainer I now made the decision to show remaining time by default - it's no
"in your face" display but in the battery's detail section - and I would kindly
ask all the people involved in this discussion to respect this. Thank you!
BUG: 290578
- Batteries are now in a proper ScrollView since in Plasma 5 popups can not (yet?) be resized
- Get rid of that expanding thing for details, it was fancy and all in 4 but doesn't play well with 5
- Use ToolTip for battery details
- Remove redundant information (non-power supply display name is always vendor + model, no need to show these in the details again)
- Make icons medium size to be consistent with Plasma NM
- More refined spacing
behavior from plasma1: the engine has an "added" value in devices
if false, means the device was already there when plasma started
therefore the applet shouldn't expand itself
this should fix the systray annoyingly opening
itself on each plasma startup
Apparently passing QDateTime::time() to the Qt.formatTime is messing
things up; might also be a Qt bug, on the other hand the docs for QTime
say that "Unlike QDateTime, QTime knows nothing about time zones or
daylight savings time (DST)".
Passing the full QDateTime object makes the applets show correct time in
all timezones.
Hats off to Andreas Eckstein for finding out this
BUG: 335050
This was used to determine if the calendar header should show a year or
not, this is now part of the component and thus the function has no use
anymore
one that probably still remain is
org.kde.plasma.systemtray/contents/ui/ExpandedRepresentation.qml:76:19: QML TaskDelegate: Binding loop detected for property "isExpanded"
that is probably causing some unwanted systray expansion at startup too
CCBUG:335482