--when changing between different views the offset
slider should not change offset values by taking
into account offset boundaries that are relevant
only to previous views
--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
--playing around with Kirigami.ShadowedRectangle in order
to provide a nice beautiful custom made panel background
that the user can chosen custom radius or shadow size.
Colors are going to be used totally based on current plasma
theme.
--new single instance editing windows revealed
an issue with buttons groups that use ExclusiveGroups
in order to identify their property. All such
implementations have been adjusted in order to
provide a more concrete experience
--that option from Behavior page is now renamed and
also its behavior has been upgraded by enabling
three possible options:
1. Disabled always
2. Auto - which is enabled for Docks and disabled for Panels
3. Enabled always
--the new approach is much more memory efficient
as the same indicator config ui is used for ALL
views and anything related to config uis is now
handled by the manager instead of each diffent
view on its own
--curent view indicator config ui is not deleted
when the PrimaryConfigView changes its parent view.
For each view there is one indicator config ui
that is kept available to be shown when appropriate.
This way we avoid unnecessary recreations of indicator
config uis when the user cycles between different views
settings.
--many plasma themes disable their shadows with
settings their opacity to zero instead of removing
their shadow elements. In such case the new approach
sets the hasShadow flag to zero
--use the original Latte trademark at all
times in Primary config view setttings. In
the past there were icon themes that was
changing Latte icon to something alientic
and that approach was breaking the Latte
trademark visual appearance.
--at first run, preset settings should be already
configured to work properly; in other case the right
click context menu does not show the correct entries
for latte/docks/panels configuration windows
BUG:423633
--provide an option for previews to work as a
popup window[new] or as tooltip[classic]
--multiple fixes to show/hide previews based on
user preferences from left click and hovering
a task
--move the active window line as the last item
of Preview column in order to be always drawn and
never overlap with previews or previous items
--used a video demonstrating multiple panels at the
bottom edge with padding between them
--max/minLength and offset are changed to float values
--max/minLength and offset can now be adjusted with
Ctrl+Wheel over their label in Appearance tab page. Clicking
the previous mentioned label will round the values
--introduce an autoSizeEnabled value in order to block
auto size mechanism when it becomes annoying. Such issue
appears more often to Latte panels
--block MenuZ from Latte icon heuristics
--improve types and references and add types splitted
at better places. So now we have
- LatteCore.Types that are global for all components
- LatteTasks.Types that are private to tasks plasmoid
- LatteContainment.Types that are private to latte
containment
--use a more logical organization for types. LibLatte2
is split to become LatteCore library and Latte types
are now moved to application level. The Latte Types will
be split even more... Tasks-Only related types will
become Latte.Tasks types
BUG:420210
--First steps in order to support mulitple Tasks
applets in the same dock and panel.
--Step1: migrate values from Containment to Task
applet.
--Step2: deprecate Task applet options that are
found in containment
--Step3: provide multiple dynamic Tasks tabs in
settings
--this way we make sure that the user will be
able to trigger showing with mouse at the screen
edge. Using the window mask to succeed in this
in not an option.
--Latte can now support multiple Views in the same screen
edge. Views as separated in THREE Layers of priorities.
1. Views from Shared Layouts have highest priority and they
are first to occupy a screen edge
2. Views that are set OnPrimary screen occupy a screen edge only
if there is NO other View from a Shared Layout applied already
3. Views that are Explicit to specific screens occupy a screen
edge only if there is NO PRIMARY view already loaded
Michail Vourlakos
Martijn Vogelaar