--ViewPart:VisibilityManager is sending events
to show or hide but it can not validate the view
visual state meaning is hidden, sliding in/out, blocked
etc. That role is taken from Containment::VisibilityManager
that accepts that signals and in case the state are
requesting is already provided then in such case
these signals are ignored.
--This way myView flags for inSlidingIn/Out/PartiallyShown/FullyShown
etc are providing valid values in some previous
problematic scenarios
--This fix solves the issue that parabolic effect with Tasks Previews
it was not too responsive but it had many glitches
--improve a lot how applets are positioned in
different alignments and more specific take into
consideration the background roundness and the
items specified length margin in order to provide
always the most consistent look for the user
--at the same time improve a lot background length
calculations and various alignments published
layout geometry in order to correspond much
better to real visible estate
--using hidden VisibilityManager::floatingGapWindow
implementation in order to provide full access for
the area which is below the screen margin when the
user has disabled user interaction for that area
BUG:433820
- Hide Thickness Screen Gap scenario provides two different struts thicknesses.
--- [1] The first struts thickness is when there is no maximized window and is such case
--- the view is behaving as in normal AlwaysVisible visibility mode. This is very useful
--- when users tile windows. [bug #432122]
--- [2] The second struts thickness is when there is a maximized window present and in such case
--- the view is hiding all of its screen edges. It is used mostly when the view is wanted
--- to act as a window titlebar.
BUG:432122
--following new norms and styles the struts
applying for Always Visible they now take into account
the screen edge margin and apply the same margin
also at their head thickness margin. If there is
much negative user feedback this might be reverted.
BUG:419731
--when a floating view is hiding its screen gap
there is no reason for struts to be added
during that phase. Published struts could be
the final expected window position in that case.
BUG:431255
Alexander Lohnau
Michail Vourlakos