--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.
--by using the new approach from plasmaviews that take
into account paddings, any hacks to activate applets through
other codepaths are not needed any more.
--new kde frameworks have solved the main issue
of very big shadows for very narrow background
thickness. On the contrary a secondary issue occurs
that in the previous case the shadows are masked
outcut for ShadowedRectangle implementation.
--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
--the multilayered background first layer is not
decoupled and is not the parent layer for all the
rest layer. This way we can really hide it without
influence the rest background layers.
--when background custom radius and shadow
are applied the dock window geometry shouldnot
change if these values are not altered. This
is especially true when a dock is hiding
its screen edge margin when there is a maximized
window and the same time is hiding also its
background shadows. In such case in the past because
shadows were temporarily disabled the dock was constantly
changing its geometry
--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.
--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
--after view startup real floating panels that are hiding
their thickness because of maximized windows must reposition
themeselves in order to have a valid visual state
--inEditMode is now updated directly from
containment()->inUserConfiguring()
--add again hiding blockers when View gets
into edit mode. That was lost during last commits
because it was part of Visual qml code that
has been moved to another window.
--Plasma::FrameSvgItem margins are not consintent
in order to provide helpful hints how plasma theme
panel-background svg is drawn properly. The new
approach calculates paddings based on top,left,bottom,right
svg elements and in that way a consistent a properly
background.minimumThickness is discovered.
--in justify mode the centered applets are now
offseted when overlapped from side layouts
in order to always present to the user all applets
and at the same time improve accesibility. That
approach takes into account how plasma panels
in 5.19 behave when the user has added auto-centered
plasma spacers.
--Can above Fullscreen windows under x11 ignore
GTK_FRAME_EXTENTS totally. Long story short
such docks can not have beautiful snapping from
kwin and as such the blur area should ignore the
headThicknessGap
BUG:422313
--was changed to 60Hz from 20Hz and also
the first call is immediately draw and then
the timer in triggered in order to block all
other calls. Hopefully this will be enough
for smooth moving blurring areas.
BUG:422209
--The new implementation for snapping needed to remove
the touching view edge from touching algorithm. The
windows trakers now provide two separate values for each
touching.
----First value is for regular window touches for which
their window geometry intersects with view published
absoluteGeometry
----Second value is for windows that are touching
view edge without intersecting with view geometry
--implementation is much more concrete now and we
need to be 1px precise in order to provide good
snapping and dodge visibility modes correctly
--in upcoming commit the view is touched property
will mean without window is touching the view edge.
For view edges touching there will be a different
variable that can be used from containment and
applets.
--dont add length edge margins through offset
for start/endlayouts, much cleaner and visual
pleasing to the eye. the user can always add
spacers if prefers to add padding.
--in configure applets mode when the layouts overlap
with main centered layout then visual feedback is provided to
the user in order to help him understand in which
layout each applet belongs
--really handy and beautiful in order to confirm the
calculations that are valid. Already a bug was found
for ParabolicEffect. There is 1px difference between
hovering Tasks and Applets
--View recreation path was broken from new implementation
for Latte::Interfaces that pass objects to containment
interface. This is now fixed and Interfaces::View object is updated
and broadcasted correctly when changed
--when GtkFrameExtents are zeroed for behaveAsPlasmaPanels
then it is better to recreate the view to avoid freezes and
hidings of the view because of compositor strange behavior
--plasma themes because of their svg nature can
have a minimum padding under which they are not
drawn correctly. In such cases background shadows
overlap and background internal drawing overlaps
in the center. That property protects from
such case by introducing a minimum background
thickness at all cases. Good example of the issue
is observed in behaveAsPlasmaPanel(s) that are
floating and have very good round corners.
--AppletItem::clip was introduced in order to
avoid circumstances that applets exceed their limits
and as such still events from surrounding applets.
Because of that change applets should now apply
their layout properties as valid all the time
--use a single slot when View triggers its workarounds
for the kwin issue that kwin hides panels when an activity
stops. In such case the view shadows are also redrawn.
--in older version screenEdgeMargin == -1 was meant
that the screenEdgeMargin was disabled but this does not
need to be passed to View any more because variable
screenEdgeMarginDisabled is now passed directly
--Blur area is not updated instantly any more
and does not make too many unnecesary calls.
A timer was added to orchestrate this in order
for the Effects area to be updated at maximum
20times/sec.
--Dont animate the view container at all cases, that
creates a much smoother experience for the user in
editing mode
--applets are now always take into account the splitters
placement and the splitters try to be always in the
center. This is much more predictable and understanble
from the user
--I have managed to solve most of the issues that were
preventing a live demonstration of applets layout
during InConfigureApplets mode... Things are more
intuitive now are updated correctly between different
layout areas... enjoy...
--container fill calculations are now tracked much
better when they are applied.
--as an improvement fill calculations are now taking place
at all edit mode states. So inConfigureApplets mode
the fill(s) applets do not throw out of screen
applets that are the layout edges
--a new implementation is needed which is going
to be simpler and lighter. Removing the current
implementation, parabolic effect works just fine
without issues and feels more responsive.
--the new implementation relies on items in order to
forward scale signals properly to their neighbours. So
parabolic effect does not have to know separators and
hidden items any more. As it appears it is lighter
also and more responsive. This is a very important
milestone for the parabolic effect.
--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
--an better plural naming was chosen in order for
for consumers to distiguish abilities purpose. Abilities
are designed to be use by multiple applets and
containers
--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
--introduce AppletAbilities qml library which is going
to be available to all applets to use it freely. In the stage
all components will be qml-only but in the future when
any of the components have been stabilized for their
apis then many of them could gain c++ implementation
--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
--the new infrastructure can remember settings between
CustomBackgroundStyle and ColorStyle in order to
help the user to not have to reassign values
when changing backgrounds, between predefined
colors style and custom one.
--plasma durations can mess up the Latte animations
experience a lot. We now use our own set animations
durations which are independent of what the user
chose for plasma animations speed.
BUG:418883
--behaveAsPlasmaPanel can now slide in/out as real windows
but after they hide there is a chance that their geometry
should be updated. This patch makes sure that this will
happen exactly before the BEHAVEASPLASMAPANEL starts
sliding-in.
--when the user has chosen to hide the screen gap
when there is a maximized window in the screen and
at the same time the View behaves as plasma panel,
it now slides in/out nicely
--the user can now choose for vertical views to
stick their edges at the top or bottom screen edge
and ignore any top or bottom views accordingly. These
options are available in the Transparent Settings
area for vertical views and in advanced settings
mode.
--improve calculations for Effects area during startup
and at the same time when the dock is totally hidden
so it should not paint any effects area at all.
BUG:416928
FIXED-IN:0.9.9
--a new Wheel action is introduced to Tasks and
the user can now choose to disable wheel actions
only for tasks OR cycle through grouped tasks OR
upwards cycles trhough grouped tasks and downwards
minimizes them.
BUG:416096
--in editing mode the panel background blur takes
into account inside the qml window, it is used
as a demonstration for the user. This patch
takes into account the blurred area roundness
in order to not blur faulty areas that are not
going to be blurred in the end.
--add a mouse wheel delayer like in other Latte
MouseArea(s) in order to limit the actions
executed through mouse wheel in one second.
The user can now execute five actions at maximum
in one second.
--mouse wheel can now be used from panel empty areas
in order to minimize windows or cycle between them.
The action is called ScrollToggleMinimed. When that
option is used the user can also use Ctrl+ScrollUp
in order to maximize a window or Ctrl+ScrollDown
to restore it
--floating views is a strange situation for which
plasma theme do not have any way to be protected for
their drawing (there is a chance that shadows and content
overlap). Latte in order to protect from that situation
now uses the auto-discovered plasma theme roundness to be used
in order to calculate the minimum thicknes for panel
background.
--enabledForApplets and lengthPadding for indicators
has now moved to indicators responsibility to handle
--as a consequence usesPlasmaStyle has been removed
from indicators API. The corner cases that indicators
conflict with plasma theme applets should be handled
differently and in a different way
--different applets situations request different
margins for indicators and margins between them
in order to draw them properly. This fix takes
into account when edge margins are disabled from
wrapper and in that case the edge margins for these
are calculated bettter.
--requesting from users a different way to remove
the Latte Tasks plasmoid if they want to is not
a good hig. Reenabling the classic ways to remove
Latte Tasks. The user can now use the applet tooltip
to remove it or by right clicking it in Latte
edit mode. Because of this the Tasks->Recycling
button is not needed any more.
BUG:415274
--provide a new way to identify which application
launcher has the highest priority in order to be
triggered. When an application launcher applet
has a global shortcut assigned to it then that
application launcher applet has the highest
priority in order to be triggered through
"Super" global key.
--block default-autopositioning for Layouts when the user
is changing location for the View. This way we are
trying to avoid issues concerning animations and glitches
during that animation.
--it is safer to block/unblock view hiding based on
edit mode animations. This way any view hiding mechanisms
are applied only after the containment editMode has
really applied.
--when the view settings window is closed then the
View must return to normal mode and disable
the editMode. In qt 5.14 default states that have a "when"
property do not play well
BUG:412940
--improved settings for Floating windows in Behavior
tab and add a new option to hide ALL screen gaps meaning
both length screen and thickness screen gap when there
is a maximized window in the screen
BUG:415630
--when the user has enabled dragging/moving active
window from floatings screen gap then that space
can not be used to activate applets. It is rather
used to drag/move/restore last active window.
--screenEdgeMarginEnabled value is not really needed
to applets and indicators. Only the margin value
applied is of importance in order to place themselves
properly.
--use screenEdgeMargin in order to support more border
styles for custom background component that paints
the underneath panel background for smart coloring.
--applets can now use the screen edge margin value
in order to follow Fitt's Law for floating docks/panels
if they want to. Latte takes case all applets of
course but in case an applet would like also to
to use also the space between the gap of the view
and the screen edge, it can so.
--when the application launcher is not a popup then
we do not have to wait for the dock show we can execute
the activation code immediately
--when Latte activates an entry can now understand
if a popup is going to be shown in order to delay
the execution. If a popup is NOT going to show either
for a latte task or an applet then the code is executed
immediately
BUG:415417
FIXED-IN:0.9.6
--Latte panels when they touch each other are informing
each other in order to provide consistent appearance. For
example the Unity mode where a top panel and a left panel
exist at the same time. In such case if the left panel is
INBUSY background state then the top panel is informed and
because inBusy state also. This way the top border of left dock
background does not look out of place. ON THE OTHER hand if
the left dock is hidden because the use has chosen auto-hide
visibility mode or any of the dodge(s) choices then the top
panel does not have to stay in isBusy state. The patch fixes
this by applying this behavior only when the left dock is shown
e.g. the mouse has entered the dock or the dodge mode is not
activated
BUG:415347
FIXED-IN:0.9.6
--automatic icon sizer is using a prediction
algorithm in order to decide to grow or not the
items size. There is a chance that the prediction
calculations are executed too early and as
such grow/shrink limits it is better to not
be to near to each other. That approach should
make the AutomaticItemSizer implementation a little
more robust.
Michail Vourlakos
l10n daemon script
Martijn Vogelaar
Yuri Chornoivan