--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
FIXED-IN: 0.8.3
--copying the new improved behavior for applets
that fillWidth/Height such as plasma taskmanagers
and in that way support them beautifully for
Left/Center/Right alignments
--fix wrong placement at multi-screen environment
during startup. freeEdges function was not sufficient for
reconsiderScreen() because there was a chance to
exclude edges that even though they were available
it returned fault results. Such case is when
a view request available edges for specific screen
and the edge of that specific view is also exluded
because that view has not finished its movement
to the new assigned screen.
--fix re-adding an explicit dock when its screen
is activated. A check was missing in order to
confirm that a primary dock is occuping that
edge but we must check also that the primary
screen is the same with the explicit one.
--add/improve debug messages
(cherry picked from commit 0bab344682)
BUG: 399456
FIXED-IN: 0.8.2
--dont call costly syncGeometry when drawShadows
externally is called. In such case only updating
shadows/borders is needed.
(cherry picked from commit be7bbfe848)
--try to make screens assignment and window geometry
more consistent. There are three variables in a dock
window for its screen and positioning to be accurate,
screen(), m_screenToFollow, m_screenToFollowId
BUG: 399456
FIXED-IN: 0.8.2
(cherry picked from commit f955c6a40c)
--the new code contains more comments and except
blacklisting all NET::Properties2 signals that are
not accompanied with NET::Properties it also
whitelists specific states for NET::WMState.
This should lower a lot the calculations needed
in order to support the dodge visibility modes.
At the same time apps that are abusing X11 signals
should be ignored totally because the whitelisted
states and NET::Properties are only set by the
user or the window manager.
BUG: 399149
FIXED-IN: 0.8.2
--when back/forward media buttons in previews
where disabled and the mouse was hovering them
then the preview was hiding itself and the
previews experience was broken.
--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
--when the user was hovering the preview player
buttons the preview was hiding itself. This patch
fixes the situation in order to identify properly
that the mouse is still in the preview in such
case.
BUG: 398962
FIXED-IN: 0.8.2
--multi-screen fix for explicit docks. There were
cases that explicit docks during startup were
moving to onprimary screen even though they shouldnt
based on the new multi-screens implementation.
Bug was tracked down at a faulty series of signals
that were overwriting dockView config values
to default values and that was creating the fault.
-- one more fix for multi-screens, a missing return
statement in case an explicit dock is called and its
edge at that specific screen is occuppied by an
onPrimary one.
BUG: 398219
FIXED-IN: 0.8.1
(cherry picked from commit 09fe5e385b)
When there was only one latte dock and the last
active window was closed, the dock wasnt showing
afterwards. The dodge logic now has been improved
in order to not lose any window manager signals
that could help indicate when to show/hide a
dodge capable dock
BUG: 398052
FIXED-IN: 0.8.1
(cherry picked from commit 203c740980)
--fix also a case that the user hasnt enabled to
show panel background at all from the Show option
and the shadows where shown because they were
chosen before it was disabled by the user
(cherry picked from commit 0f79c08e86)
--when the user had chosen monochrome contents and had
disabled the panel background totally the case wasnt
activating monochrome contents when needed
(cherry picked from commit fc8a531837)
--do not consider preferredWidth or preferredHeight
for applets when that value is <=0 otherwise that
applet it may become invisible. Such case is the
plasma analog clock when it is locked at a vertical
dock
BUG: 398098
FIXED-IN: 0.8.1
(cherry picked from commit ec0e16ca5a)
--there are cases that the window manager doesnt
return any active window at all. In such cases
we can assume that our docks/panels dont have to
be hidden.
BUG: 398052
FIXED-IN: 0.8.1
(cherry picked from commit 66817695fe)
-- 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
(cherry picked from commit b4dd016ed0)
make sure that we delete a valid contextMenu and
not a ghost reference. This could occur from
two-fingers emulating right-click in wayland.
BUG: 397635
FIXED-IN: 0.8.1
(cherry picked from commit afb34a85cf)
when the plasma theme was not supporting shadows then
Latte was double drawing the panel background when
the user has chosen that wanted shadows
BUG: 397980
FIXED-IN: 0.8.1
(cherry picked from commit 87094a6fe7)
--many plasma themes provide a different panel
background per edge, with different styles or
transparency levels. Latte now respects the
plasma theme concerning the panel backgrounds
found in a plasma theme.
(cherry picked from commit 81d3a12e91)
--if a dock/panel was containing a systray there
was a chance that the systray was messing the
calculations for adding/removing docks based on
the screen and edges changes
(cherry picked from commit 285a2f8764)
--Latte will no longer try to be too smart concerning
the multi-screens behavior. At the old implementation
Latte wouldnt let you reach at a state that you dont
have a tasks plasmoid available. Such a case could be
when the user moves a dock from primary to explicit
screen and disables the screen afterwards. That case
should be thought better in the future in order to be
identified and handled properly without making the
code unnecessary complex. Such an example could be by
identifing the case and asking the user for actions.
(cherry picked from commit b2f1f98b57)
--there are cases that the window geometry isnt consistent
for maximized windows. That was breaking the previous
implementation of dynamic background because of:
https://bugs.kde.org/show_bug.cgi?id=397700
the new implementation is using only the window center in
order to identify the screen in which a window is
present
BUG: 397344
FIXED-IN: 0.8.1
(cherry picked from commit bb8835f156)
--the background contrast effect should be applied
only when the dock/panel is visually solid otherwise
it may block the transparency settings
BUG: 397431
FIXED-IN: v0.8.1
(cherry picked from commit 78b41eff91)
Michail Vourlakos
l10n daemon script
Tobias C. Berner