Instead of keeping a copy of Kirigami's About page adapted to
KPluginMetaData, pass the widget's metadata to Kirigami.AboutItem.
This also brings Kirigami's reflowed license text, so the license no
longer shows the hard line breaks of the license file.
BUG: 486305
We use PreserveAspectCrop for the 16:9 card preview of the wallpaper
instead of stretching them. We also request a square thumbnail so that
wallpapers narrower than 16:9 come at least as wide as the card and do
no need to be upscaled.
BUG: 478784
since the activity switcher/widget explorer are dock windows,
positioning
is completely managed by layershell, and we can't put it on top
of another panel, so if there are horizontal panels, make the
window less tall to accomodate that.
BUG:527158
in the no-password scenario we previously ended up unlocking even
further, causing unexpected auto-unlocks. instead stop the
authenticators machinery and do not try to unlock when already unlocked
CCBUG: 526194
when we deal with no password scenarios we previously entered a not very
well defined unlocked state where the user had to click a button to
actually get rid of the ui. instead encode this as a property and stop
the authenticate machinery when unlocked. notably prevents automatic
unlocks because of the start timer
CCBUG: 526194
BUG: 515103
Currently when the vkbd opens, the panel floats because KWin resizes the
window away from the panel (even for fullscreen windows). Factor in the
virtual keyboard state into whether the panel should be floating.
The Widget configuration dialog is supposed to only show a top and
bottom separator if the contents are scrollable, but not if it's a
List/Gridview-based kcm (as those handle scrolling internally). The
GridViewKCM detection is broken though: it tests whether the page's
flickable is an instance of GridViewKCM, but it isn't - the page itself
is the GridViewKCM, not it's flickable, so it will treat it like a
regular page and draw the separators if the GridView is flickable.
Instead, test whether the current page is a GridViewKCM. This only
affects the Sticky Note config dialog, as it's the only GridView-
based one.
this restores previous behavior where the password authentication is not
showing the prompt by default.
this can be enabled by the user with the kscreenlockerrc config
```ini
[UI]
ShowPromptInRegularAuthenticator=true
```
This reverts commit 1e77a2df15.
Some references to the footer were not fixed, breaking the login method:
file:///usr/share/sddm/themes/breeze/Login.qml:65: ReferenceError: footer is not defined
It removed sessionButton which is still needed and referenced, which
also broke login:
file:///usr/share/sddm/themes/breeze/Main.qml:245: ReferenceError: sessionButton is not defined
Had comments noting to keep the implementations in sync between the
lockscreen and sddm versions, not ideal.
Port to a reusable component in plasma-workspace, so they can both use
the same one without concern of keeping them in sync. Also will allow
plasma-login-manager to become the 3rd consumer of this component
without further duplicating code.
- Make sure all buttons have text set
- Make sure all buttons have tooltips that appear on focus
- Disambiguate the two "Configure" buttons so that screen users can tell
them apart, especially when using a screen reader
BUG: 519306
FIXED-IN: 6.8.0
Now the logout screen's interactive controls are displayed only on the
active screen and follow the pointer when it moves between screens,
matching the behavior of the lock screen.
ENHANCEMENT: 431382
FIXED-IN: 6.8.0
Amends 06675e18ef.
When a wallpaper provides an explicit accent color, Desktop.qml assigns
it to the desktop. However, the following independent if statement
immediately replaces it with the dominant color calculated from the
wallpaper image.
BUG: 514656
Immediately close the configuration on Ok and then actually apply the
configuration, which works fine as the dialog is not immediately
deleted.
In combination with
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/6766
It makes possible to not reopen the configuration dialog after ok
is clicked to accept a containment layout change
BUG:389109
Remove version numbering like from elsewhere to avoid any
issues with matching the surrounding system.
ActivityItem was unclickable due to the dropEnabled setting
the visibility of dropArea false, and that caused the
onClicked signal never fire as it did not listen for clicks.
Set it to true instead.
If a user has enbled the SlowKeys filter in Accessibility settings, show
this in the lock screen. This is similar to CapsLock being enabled, as
it might be very confusing for a user that forgot about SlowKeys.
Depends On: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/6626
I've decided **not** to include the feedback from [https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/3660](https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/3660) . I could not continue that MR as I failed to push to that branch again (I'm new to git, it's most likely something I've done wrong in my setup, sorry!)
Reason for not including the feedback:
There's currently three potential messages that could be shown: CapsLock Enabled, SlowKeys Enabled, and "root notification" (which I'm not quite sure what they are). Having something along the line of "CapsLock and SlowKeys are enabled" as suggested would potentially become quite complicated, if we also show more message, e.g. "Bounce Keys Enabled". This would lead to quite some possible combinations, blowing up the code and having multiple strings to translate.
I'm open to boldening parts of the string (e.g. **CapsLock** or **SlowKeys** etc.), though the root.notifications are probably not bold ?
| After | Before |
| ------ | ------ |
| {width=375 height=600} | {width=375 height=600} |
@teams/vdg
@teams/usability
If there are multiple windows under a parent window as
their transientparent, and if there is one visible
child window in the focus, all the windows will
report being active.
See QTBUG-146992 for more.
When dialog is not visible, set the mainItem disabled,
so that we do not send any unnecessary keyboard shortcut
signals to anything it holds, as they still are
active even if they're not visible.
BUG: 515280
Instead of blocking password entry for a fixed time in QML (regardless of the actual timeout pam configures),
we instantly allow sending a new password attempt. If this attempt comes in while we're still in the actual pam timeout,
we queue it to be applied after the timeout ended and disable the password field while it is queued.
The lockscreen has a button for suspend that was written in early days
of QML where we were injectinng context properties and introspecting the
metaobject of the root object.
Since then we have a QML import for suspend and hibernate. We were using
this import already for various features.
This allows for cleanup on the kscreenlocker side.
<!-- Thank you for submitting a merge request to make KDE Software better! Use the information from the commit message(s) to fill in the template below.
(For future reference, follow the guidelines at https://cbea.ms/git-commit/#seven-rules)
-->
### Original commit message(s)
* Adjust CMakeLists
* Move margins separator to plasma-workspace
* Add margins separator menu item
### Reason for the change
Similar to [panel spacer](93305c464e) the margins separator should not be placed on the desktop because it does nothing there
Sibling merge request: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/6494
<!--
If this merge request change is resolving a problem, describe the problem and explain why the approach taken here is the correct way to resolve it.
If the merge request adds a new feature or UI change, explain the benefits of the change.
-->
### Test plan
<!--
Extend any related autotests with new test cases to validate your changes. If none exist, consider adding one if you have the technical skills to do so.
Otherwise, at least describe how you tested the change, and how someone reviewing this merge request can test it themselves. No need to mention obvious things like "Apply the changes".
-->
### Screenshots or screen recordings
{width=555 height=561}
<!--
If this merge request introduces a visual change, please add before-and-after screenshots in the following format:
| Before | After |
| ------ | ----- |
| [drag "before" screenshot here] | [drag "after" screenshot here] |
-->
### Bugs fixed
<!--
If the changes in this merge request fix any Bugzilla tickets, add the following keyword for each one:
BUG: [number of the bug report]
-->
The panel focusing shortcut requires modifier+key shortcuts, but
activating widgets can be done modifier-only. This feels inconsistent,
and having a modifier-only shortcut to focus the panel may be convenient
for some users.
Instead, allow modifier-only shortcuts for the panel focus shortcut as
well.
