--each origin mouse area is now informin
the SunkEvents handler for the relevant
origin areas at the same time and this way
there is no events breakage when changing
from one sunked event origin area to another
--the sunked events origin and destination areas
are now released only when the event is NOT inside
any origin area or any destination. This way
no events breakage is appearing when changing from
destination area to origin area and vice versa.
--move internal synced launchers infrastructure
in order to use Launchers Ability. Things
this way will become much cleaner and
at the same reusable and maintainable
--when struts thickness during startup was zero
that was creating an invalid window geometry under
wayland and subsequently it was crashing the app.
BUG:431381
--when a floating view is hiding its screen gap
there is no reason for struts to be added
during that phase. Published struts could be
the final expected window position in that case.
BUG:431255
--each applet has now its own Sunk events to handle,
and as such each applet can now have different paddings
and that does not create any issues or missing events
--use only input events in order to identify the area
from which a window accepts input and also remove almost
every mask-qml code handling
--by reducing mask usage to minimum we fix also the
BLACKLINE bug under X11
-- The new approach reduces mask area calls to
barely minimum. Input mask is used instead to
specify the area for which we accept input.
-- The new approach solves also the BLACKLINE issue
when hovering the view at startup. This is because
at all times the full window area is drawn.
Recently support for window thumbnails on Wayland was added in
latte-dock, but it shouldn't work as is because the screencast protocol
is not listed in X-KDE-Wayland-Interfaces. Only "trusted" applications
can bind the screencast global.
--more specific identifying properly when a vertical
view is shown and is touching a top or bottom view
that has requested to be fully trasparent when no
maximized window exists
--when the user requests a specific layout in Multiple
Layout mode the new approach is the following. If
the layout has assigned activities this is respected
but if its activities are empty that layout is assigned
only on the current activity and any other layouts assigned
explicitly to that activity are released
--the controller does not need to host its own
CentralLayouts any more. It retrieves original
data for Synchronizer, updates layouts accordingly
and sends back to Synchronizer all the updated
layouts data
--Move in a simpler layouts approach.
--Single Layout mode loads ONLY ONE Layout for ALL Activities
--Multiple Layouts mode loads any combination of Layouts based
on the following settings:
-- OnAllActivities
-- ForFreeActivities
-- SpecificActivities
--PlasmaExtended::Theme produces QRegions based on corners
radius that can be consumed afterwards from Effects calculations
in order to provide correct QRegions for custom backgrounds
produced from custom background radius option
--Export For Backup, exports a layout with its entire
configuration for ALL applets
--Export As Template, exports a layout after the user
has chosen which applets should keep their settings
and personal data. By default Latte Tasks plasmoid
is going to propose to keep its data because no
personal data are kept in it
--onSomethingChanged syntax is preferred for all
slots that are triggered from somethingChanged signals
--doThis syntax is preferred for generic slots that
are triggered from various different codepaths
Michail Vourlakos
l10n daemon script
Vlad Zahorodnii