Merge lp:~dandrader/qtmir/dontOccludeFreshSurfaces into lp:qtmir
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Gerry Boland | ||||
Approved revision: | 559 | ||||
Merged at revision: | 559 | ||||
Proposed branch: | lp:~dandrader/qtmir/dontOccludeFreshSurfaces | ||||
Merge into: | lp:qtmir | ||||
Diff against target: |
61 lines (+22/-4) 2 files modified
src/modules/Unity/Application/mirsurface.cpp (+16/-4) src/modules/Unity/Application/mirsurface.h (+6/-0) |
||||
To merge this branch: | bzr merge lp:~dandrader/qtmir/dontOccludeFreshSurfaces | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Gerry Boland (community) | Approve | ||
Unity8 CI Bot (community) | continuous-integration | Approve | |
Review via email: mp+305036@code.launchpad.net |
Commit message
Don't occlude newly created surfaces until some time has passed
Ensures apps are able to render the initial state of their UIs straight away.
The main use case is the dash being created behing the greeter/lockscreen (and therefore occluded) on device start up.
Description of the change
* Are there any related MPs required for this MP to build/function as expected? Please list.
No. Had exposing the age property left as a TODO exactly to avoid the pain of having companion unity-api and unity8 branches, which would, besides slowing down the release of the fix, also cause new conflicts on the ongoing https:/
* Did you perform an exploratory manual test run of your code change and any related functionality?
Yes
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
N/A
Turns out dash takes longer than I expected to get itself together during device startup, hence the 10 seconds, which has some spare room. Tried 3.5 seconds before and it wasn't enough, for instance (on mako).