Summary:
This fixes a problem where window thumbnails are no longer visible since KDE Frameworks 5.55. This is caused by https://cgit.kde.org/plasma-framework.git/commit/?id=b257029afc3bfcd6366d2c2b910b8d91403ab8a which no longer automatically updates the visibility of mainItem of PlasmaCore.Dialog.
BUG: 404234
Test Plan: Ensure window thumbnails are working correctly now
Reviewers: mvourlakos
Reviewed By: mvourlakos
Subscribers: plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D19002
Summary:
Changes in libtaskmanager in Plasma 5.15 currently break several Latte Dock features. This patch ensures that Latte Dock will continue to work when Plasma 5.15 is released.
BUG: 403358
Reviewers: mvourlakos
Reviewed By: mvourlakos
Subscribers: plasma-devel
Tags: #latte_dock, #plasma
Differential Revision: https://phabricator.kde.org/D18375
Summary: Fix minor typos in messages and comments
Test Plan: No major changes to prevent compilation and usage
Reviewers: mvourlakos
Reviewed By: mvourlakos
Subscribers: plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D17894
--the luminas functions didnt work well
for all cases. Latte is now using brightness
functions as described at:
https://www.w3.org/TR/AERT/#color-contrast
this patch fixes all cases mentioned in the bug
that Latte contrast identification did not work well
BUG: 402115
--moving a task now is not synced immediately to
other docks. Syncing takes place only in the end.
The dock in which the user changed the launchers
order sends a signal to other docks to update
theirs launchers order.
BUG: 401232
--dropped paths/urls on launchers of Global or
Layout launchers group did not open because the
synced infrastructure was breaking the QJsonArray
in that case.
FIXED-IN: 0.8.2
-- there are cases that hiding previews too early
can create crashes under wayland. Such a case is
when the user uses the touchpad to emulate a right-click
event to create a context menu for specific task
BUG: 397635
FIXED-IN: 0.8.1
--previews showed some strange behavior by
re-introducing faulty or empty previews under
X11. Best way to approach this is to follow up
plasma design idea in order for the code to be
comparable. The code was updated and the introduced
issue shows to be fixed but this wants users
feedback.
BUG: 397193
FIXED-IN: 0.8.1
--with this commit now Latte is able to identify what are
the global shortcuts used for each activation entry and
also to not show at all any badge for activation entries
that are disabled from the user
BUG: 397128
Clicking a task group shows a tooltip with list of tasks. This tooltip
cannot be controlled by keyboard and it will stay open unless mouse is
used.
This patch changes the behavior so that when a global shortcut activates
a task group (usually Win+1, Win+2 etc.) a next task in the group is
activated without showing a tooltip.
During dock sliding-in because the parabolic
effect isnt trigerred immediately but we wait
first the dock to go to its final normal
place we might miss the activation of the
parabolic effect. By catching that signal
we are trying to solve this.
-- disable the use of PlasmaCore.WindowThumbnail
under Wayland in order to fix a crash that was
appearing after a while when the user was using
previews
BUG: 392865
-- when removing a task and there are surrounding
separators then the hidden spacers are updated
immediately for the neighbour tasks. In such case
in order to not break the removal animation a small
margin must applied.
--the old architecture that was trying to keep
an internal separators record couldnt catch up
and at the same time could create issues with
internal separators at different activities.
--when only launchers are shown and the user
has chosen to disable any active indicator
then the plasmoid should behave only as
a smart launchers list with no window
capabilities
--when the plasmoid is hovered when the
applets hoveredIndex should be initialized
and when an applet is hovered then the plamoids
hoveredIndex should be initialized to -1.
--the directRenderDelayer is used during first
entering in order to delay the activation of
directRendering. The cons of previous fastEntering
implementation added the necessity for this
replacement.