When using a language that's wordier than English and this label becomes
a two-line string, currently the layout breaks and the string overflows
because the Label item that draws it has no maximum height and elision
mode set.
This commit fixes that by setting them accordingly, and also using a
standard icon size for the icon so that there's actually enough room for
two lines of text.
BUG: 458614
FIXED-IN: 5.24.7
We don't have placeholders in any other field in this KCM.
Showing a placeholder is good to show a default value, but showing an
example of what an email address is with an incorrect value doesn't add
anything.
when creating or deleting a user is not enough to pop the old page,
but a new user needs to be selected (either the newly created one or the
one just on top of the deleted one) so that the kcm doesn't stay
half empty with an ui that looks broken
BUG:450182
This allows it to be aligned with other form field, which is not
possible at the moment since it exists outside of the FormLayout in a
Row:ayout with the avatar. Fixing this would require adding API to
Kirigami.FormLayout to let its right side align to elements not in
another FormLayout, or port away from FormLayout and use a big
GridLayout instead. Both are messy. Instead, let's put the Name field
in the form layout and center the avatar above it.
Now the button begins with a verb and ends with an ellipsis in
conformance with the HIG, and there's also a little message that tells
the user what works and what doesn't. This should help to manage
expectations a bit.
This was added to Kirigami in
https://invent.kde.org/frameworks/kirigami/-/merge_requests/314
and simplifies and standardizes the creation of simple text-based
headers in OverlaySheet. This commit ports plasma-desktop's KCMs to
use them in all the places where it is possible to do so.
This adds the column spacing into calculation for determining how many columns there are, preventing certain multiples of window sizes from having too many columns.
BUG: 428899
Qt 5.15 introduced new syntax for defining Connections. Fix warnings like this one:
QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Right now, when a user changes their login password, their KWallet
password is not changed. For users whose KWallet password was the same
as their login password, this causes the two passwords to get out of sync,
and then the user will be prompted to unlock their wallet the next time
they log in. If they use their new password, it won't work. This is very
very frustrating if you don't know what's going on.
Now, when you change the login password of your own user account, and
you have a wallet named "kdewallet" (the default one) in your list of
wallets, you will be prompted to change the password of that wallet to
match the new login password. This is optional and you don't have to do
it, and you won't be prompted to do so if you don't have a wallet named
"kdewallet", which indicates that you have a customized KWallet setup
and you presumably know what you're doing.
BUG: 389030
FIXED-IN: 5.21
Don't fail silently when an error occurs otherwise the kcm just looks broken.
Show at least an inline message so the user knows that something went wrong.
The comment was wrong. We can distinguish why an error occured. Furthermore,
even if it is a permission denied error we do not know if the user canceled
the action or if it failed for some other reason so also treat that as an
error.
BUG:425036
CCBUG:426932
FIXED-IN:5.20
CCMAIL:uhhadd@gmail.com
Nate Graham
David Edmundson
Janet Blackquill
Marco Martin
Devin Lin
Alexander Lohnau
Felipe Kinoshita
Guo Yunhe
Konrad Materka
David Redondo