KWin restores geometry before the compositor re-commits the
exclusive zone, so the window can land partly behind the dock.
A deferred check clips the bottom edge once the round-trip
completes.
This adds a gesture handle mode to the navigation panel, which can be
enabled during gesture-only mode. This reserves space for the system
gesture to be able to be used, allowing us to extend the height in KWin
of the gesture recognition area (which is currently far too short for devices such as Pixel 3a).
This also allows for navigation with a mouse; clicking on the handle
triggers the task switcher, holding it triggers the "home" action.
This adds support for specifying options needed to deal with phone
display panel pecularities (ex. screen curves, notches, punch holes)
This is implemented as settings in ~/.config/plasmamobilerc, which can
set panel heights, paddings, and center spacings to duck display
cutouts. The pixel values are scaling independent, and so are not
affected when the display scaling is changed.
This is then exposed over DBus, so that components from outside of
plasmashell (ex. KWin) can access it easily without needing to connect to
kscreen themselves. Each screen is exposed as a single object.
Currently support is only added in the status bar and the navigation
panel.
Currently all screens have the settings applied. In the future, we may
want to limit this just to the internal screen (?)
---
This also adds a "devices" folder (in `devices/configs`) where per-device configs can be set.
This is installed to `/usr/share/plasma-mobile-device-configs`.
In `plasmamobilerc` (installed to `/etc/xdg/plasmamobilerc`, or
`~/.config/plasmamobilerc`), envmanager will read:
```toml
[Device]
device=oneplus-enchilada
```
for the device config to use and write its settings to
`~/.config/plasma-mobile/plasmamobilerc`.
This converts many of the animation durations to Kirigami units so that
they can be controlled system wide. It also speeds up several of the
animation durations (ex. in folio) from 800ms to 400ms to improve the
feel and responsiveness of the shell.
Fixes typos in various source comments.
Found via `codespell -S "*.po,*.svg,*.pgm,*.xml,./po,*.desktop,*.json,*.actions" -L aline,aparent,childs,distroname,indexin,indx,logicaly,lokal,nd,splitted,te`
Apparently i18n doesn't support string literals with single quotes as
parameters. Fix occurrences of this and add a CI check to ensure this
won't happen in the future.
The module exposes TaskFilterModel, which extends QSortFilterProxyModel
QSortFilterProxyModel is registered to QML as part of the QtCore module, so we need to add that to DEPENDENCIES for tools like qmllint to work properly
Breeze changed the icon for the "close" button to be a plain X, instead
of having a red background. Ensure that we use the complementary colour
scheme.
Fixes:
../kwin/mobiletaskswitcher/plugin/taskfiltermodel.cpp:81:40: error: ‘class KWin::Workspace’ has no member named ‘activities’; did you mean ‘ActivityRaise’?
81 | auto activity = Workspace::self()->activities()->current();
| ^~~~~~~~~~
| ActivityRaise
This occurs when KWin is built with -DKWIN_BUILD_ACTIVITIES=OFF:
https://invent.kde.org/plasma/kwin/-/blob/master/src/workspace.h#L424
This reverts commit c45f9ed446.
The kwin rules setting causes all desktop windows to have window decorations. Revert this for now until we figure out a solution.
This merge request adds a new setting to auto hide the status and navigation panels so applications will be able to fill out the entire device screen area. Also, this adds a new quick settings toggle to quickly change this property.
Replace the convergentwindows KWin script SSD toggling with KWin rules to ensure
windows are maximized and have no window border (and toggle off for
docked mode). KWin rules work immediately at window creation, which is
more efficient than listening to window creation events and manually
changing properties on them.
Currently, window rules setting maximization don't seem to address all cases where a window gets unmaximized, so for the time being we will still need the logic in convergentwindows to handle any sidecases.
Disables gesture navigation when Action Drawer, Notification Popup Drawer, or VolumeOSD are visible as activating the task switcher in these situation can feel a bit weird.
Note:
~~Draft for in till I can get side loading working again so I can test it on device.~~
Still can't seem to get side loading working quite yet. Though, I did run the test I could from my laptop and it does seems to be working fine, so I will be removing this from draft.
This fix maximizes the current window if it ever leaves a fullscreen or maximized state. This is to fix a bug where if a window exits fullscreen mode, it will not return back to a maximized state.
Most Notable Changes Here Include:
1. If the user moves and lifts their finger up halfway up the screen, the navigation gesture will now go home.
2. The task drawer will now move in and out of view depending on the gesture navigation state.
3. The app window will now continue to shrink with resistance as the window moves further up.
4. When in the task drawer, if the user drags up from the bottom, the current task will now follow the users finger like the task does when dragging up from within an app.
5. The task drawer will now slide in from the side when it is not within an app.
I would upload a video here to showcase these changes. However, I was unable to get OBS to record my screen while in my plasma mobile session.
Replace `window` icon by `edit-none` icon. The `window` icon is least
representative of what it means that the `edit-none` icon (gives more
the feeling of something being empty).
haptics are triggered when conditions are met to open task switcher or task scrub mode is engaged.
fixes related bug in task switcher gesture logic when invoked from homescreen
fixes https://invent.kde.org/plasma/plasma-mobile/-/issues/366
I'm not really sure how the metadata was installed previously, but it appears the behaviour for that has changed and we now need to install the metadata file ourselves.
doing a quick task switch gesture towards the end of the list should force open the task switcher (there is nothing to switch to)
this was half-done on the left side of the switcher (this behavior is not visible with immediate task reordering, but could be hit if we have different ordering criteria or delayed reordering)
and due to superfluous Math.max completely not working on the right side always opening the right-most task instead of opening the switcher
Fixes https://invent.kde.org/plasma/plasma-mobile/-/issues/343
This restores the sorting of tasks by their last activation. The task model now becomes a singleton and retains state even while the effect is not active, while the filter/sort proxy model is still initialized at task switcher load.
