--fix case that indicators config uis were lost totally
during recreating a view that was using a custom indicator
and that custom indicator was updated.
--fix case that custom indicators were not assigned any
more to their original views when the dock settings
window was created first time for them.
--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
Michail Vourlakos
Martijn Vogelaar