Prevent a "You don't say" moment, only show the OSD when using the mousewheel on the tray icon
to provide feedback. Also make it more finegrained and allow 5% steps on the tray icon
Needs further investigation on why it crashes but probably when the Repeater recreates
the items due to data changing somewhere.
Also use modelData to access model data.
Reviewed-by: Lukas Tinkl
Tooltips aren't particularly discoverable. This also refactors the code away from using
a string containing a HTML table (which doesn't play well with RTL languages) to a fancy
Array and a GridLayout that is shared between the battery tooltip and the main view
BUG: 337996
FIXED-IN 5.2.0
This finally allows us to have predictable sliders where a wheel whill always
result in a brightness change rather than having it go from 0 to 10 which is still
below 33% in case of 3 keyboard brightness steps resulting in no change whatsoever.
It also shows 0/3, 1/3, etc instead of percentage in such cases.
Also clean up a bit, remove superfluous clipping and prevent brightness change
on popup instantiation
- All of this ugly conditional anchoring has been replaced by layouts where applicable
- The details have been outsourced into a separate file which is loaded on demand
- Removes code duplication by using fancy Repeaters
REVIEW: 121057
Whenever a job disappears for whatever reason (cancelled, finished, error, ...) we display
a persistent "Job Finished" notification. When the user explicitly cancels the job, there's
no need to confirm since the job will be gone. This solution is not ideal since we just track
it inside the plasmoid (ie. when you click Cancel in a "Override this folder?" dialog, it will
still show the notification) but at least the obvious "You don't say" moment is gone that way.
Ideally in the future whoever is responsible for the job (KIO, ...) should be given the
responsibility for an appropriate notification since the owner knows best why a job quit.
CCBUG: 340068
According to the notification spec, the body is a subset of HTML which implies that it's the
client's responsibility to take care of escaping things that look like tags.
REVIEW: 121155
- Some minor code styling (new Array() -> [], new Object() -> {} etc)
- Pass the notification object we get from the data engine to addNotification verbatim
instead of having an ugly function with dozens of parameters we just use to construct
a similar object ourselves anyway
- Push actions into array directly instead of creating a new Object, setting its properties
and then pushing it
REVIEW: 120993
Montel Laurent
Kai Uwe Broulik
l10n daemon script
Marco Martin
Jan Grulich
Lukáš Tinkl
Sebastian Kügler
David Edmundson
Pino Toscano
Weng Xuetian
Martin Klapetek