--each applets layout can not identify properly
which applet is the first/last visible from its
contents. This way we can now identify properly
at all cases which applets should remove their
margins in order to follow Fitt's Law at screen
edges. For example when a windows buttons applet
is found at the screen edge and suddently it
hides itself then the next visible applet should
be considered at screen edge and such should remove
its margins in order to touch the screen edge.
--remove the layout exception for the plasma systray
and behave for this just all the rest applets
--fix indicators for applets in order to consider
properly the indicators padding and applets margins.
In other words the Latte indicators for applets should
not take up all the length provided but ONLY the
applet length + indicators padding (without at any
case the applet length margins)
BUG:414104
FIXED-IN:0.9.5
--when option "Hide Background when not needed" is
used on its own activates or not the forceTransparentPanel
code path. So when that option is enabled and any
window is touching the Latte::View then the force
transparency codepath should be disabled. In such
case the user background settings are applied.
BUG:414071
FIXED-IN:0.9.5
--this patch add two fixes concerning automatic
icon size when contents exceed the view maximum
length.
--A) when the function is called then it also
called one more time after 1sec to confirm that
the icon size found is valid. In the past that
approach was creating an endless loop that should
not be triggered any more
--B) the grow limit was made to be equal with
the shrink limit trying to be more predictive from
the user when the items will grow or shrink. In
the future we must take care of this if the items
grow or shrink endlessly
BUG:411860
FIXED-IN:0.9.3
--many applets are changing layouts and during that
process the main icon becomes invisile, in that case
the latte overlaied icon should also been disabled and
let applet paint itself accordingly
FIXED-IN:0.9.3
--when an applet can not be hovered meaning to use
the parabolic effect and that applet is at the far
screen edge then margins can be disabled for this applet
in order to look exactly touching the screen edge
and at the same feel right following Fitt's Law
--separators are only usings the external margins
between items. In the past it was also consider
the indicators internal padding. This is not
needed and it was creating too big empty
spaces with no real reason.
--through level.requested options each indicator
instance can request specific repositioning for
each icon. Very good example for this is the
Win7 style indicator
--when qml uses software rendering checks should be
added in order to not hide the visual elements. This
is taking place now in a more concrete way and checked
also that tasks with badges or not are still shown
BUG:411037
FIXED-IN:0.9.2
--draggingStarted signals/slots were used in order
to handle the active window dragging from empty areas.
The new approach ungrabs the mouse properly through
View relevant function and at the same time sends a
QEvent::Leave event to inform applets that the mouse
has left the view. This is enough in order to remove
any older draggingStarted workarounds and hacks.
--Latte should use the same workflow paradigm for
switching vds and activities with the plasma pager
approach. This commit complies with this.
BUG:411086
FIXED-IN:0.9.2
--when qml software rendering is enabled the ShaderEffects
do not work. Hiding sources in that case is hiding
from the user tasks and applets with no visual feedback.
Sources in that case should hide themeselves and give
the user the minimum which is the original drawn contents.
BUG:410920
FIXED-IN:0.9.2
--when a vertical view is in busy state and is touching
also a horizontal view that is fully transparent in
SMART mode then the visual result is not that good.
In that case it is better to show the view background.
The horizontal view background in that case can provide
three different states:
a) if the panel style for popups is activated then the
horizontal view will follow the plasma original style
b) if NOT [a] and solid background for touching windows
is enabled then solid background will be offered
c) if NOT [a] and NOT [b] then the isBusy state
transparency will be offered
--trying to increase smartness for horizontal
and vertical views. In multiple layouts environment
a view can exist in cases that one or more of
the sided views that is touching it is NOT
transparent, it would be nice for those
cases the top or bottom view to LOSE also
its transparency in order to not look
inconsistent.
--the new implementation supports and always darkish
case when the isBusy background is drawn. So now
we have the following possibilities:
a)panel transparency<35 means BEST contrast with
underlying desktop background
b)panel transparency>=35 AND <70 means a DARKISH
background
c)panel transparency>=70 the user chosen plasma
theme
--absolute geometry is the published area that the
dock/panel occupies when it is shown. So it should
not change when the dock becomes hidden. This patch
fixes the case for the !compositing environment.
--this was noticed when the user was removing an applet
through the context menu and at the same time this
applet was zoomed. With this patch the parabolic effect
behavior returns to normal
--the user can now choose to enable or NOT 3D
style for all badges through Latte Global Preferences
window. By default the Flat style is preferred
BUG: 409467
--reconsider/fixes applets axis blocking for parabolic
effect when unblock it also when applets are updating
their properties. This takes place only when
applets zoom factor === 1 (in normal mode) otherwise
the parabolic effect may broke
--The user from Tasks,Badges can choose a more prominent
color for notification badges (usually reddish). In case
the user has not enabled that option(default) then the plasma
theme highlight color is used which is also the default
option of Latte v0.8
BUG: 408955
--DragDropArea in containment should not activate
mask update (animationsNeedLength) if the dragging
is not valid for that DragDropArea. A good example
for this is when the user drags Tasks, in such case
the DragEnter signal is ignored and the DragLeave
may not reach to containment. In such case the
animationsNeedLength signal should NOT be sent
BUG: 408926
Michail Vourlakos
Yuri Chornoivan