--ListView is anchoring its children very strange.
This was creating circumstances that the children
were anchoring themselves wrongly e.g. when removing
them and in some animations. This commit introduces
heuristics (workarounds) for these cases. The
broken anchor situations are protected by introduced
correct anchors from our qml side in listview
child items
--by taking account the libtaskmanager way of doing
things. Latte is trying to delay the removal of the
launcher in order for the animation to play correctly.
At the same time if a window or startup is added is
not shown if there is a waitingLauncher(animated launcher)
until this launcher completes its animation
--import launchers and use new architecture,
an new record in settings is appearing called
launchers59
--this patch works only from plasma 5.9 and above
--it gives many improvements such as the "pin" feature
and the explicit launchers can be placed even
between global launchers
--this patch supports activation through shortcuts
--Meta+number, activates the relevant task, for
groups by default it activates the next available
window in the group
--Meta+Ctrl+number, create a new instance for that task
or launcher
--the user should know that must first enable these
shortcuts at plasma global shortcuts configuration
window
--icon margin is not set by the user,
this is why the hidden spacers must update
their size according to the user choice,
do not create to much empty space at the
edges
--relevant to #250,creates consistency for
hovering tasks and applets. The only concerns
is around the springanimation introduced in
plasma 5.10 but this will be checked later
how it can be supported properly
--this a big fix for the painting mechanism.
Introduces a new direct rendering phase in
which no delays are happening on drawing.
This commit contains also the fixes in various
places in order for the new rendering to work
correctly
--this improves the way tasks geometries are
published for the windows. This improves the
experience for the minimize kwin effects. With the
old code there were many cases that the animation
was broken
--when a task is removed too fast then some
animations were not informed that had ended.
So there was an addition animation signal but
no removal animation signal. This fix protects
this in two different cases
--the normal state also from now own uses only
the animations states and no the hovered task
indicator. This simplifies things a lot and probably
creates also a much robust experience.
--the infrastructure is in place in order to not
need the automaticAnimationLength flag. From this
commit masking based totally only on animations
flags and on hovering indexes