diff options
| author | Wale Ogunwale <ogunwale@google.com> | 2015-09-30 10:09:39 -0700 |
|---|---|---|
| committer | Wale Ogunwale <ogunwale@google.com> | 2015-09-30 10:20:25 -0700 |
| commit | fd04d8c8840c2a762e4f19c31310561263898621 (patch) | |
| tree | 55afb3e548e82a592f4c93cc0d689e0eb788979b /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | b186388b673035f3a19bcc5d6f9dd8545549a224 (diff) | |
Initialize DisplayContent base info when object is constructed
It is possible for an external process (e.g. sys-ui) to call into
WM to get the bounds of a stack in between the construction of the
DisplayContent object and SystemServer telling WM that the display
is ready. Incorrect bounds would be returned to the caller in this
case since the baseDisplayWidth/Height is only set when the displayReady
call is made.
We now initialize the base display information when the DisplayContent
object is created so any call to get the logical display rect of the
display will always return the right bounds. This should be okay as the
display manager is initialized way before window manager.
Bug: 24505761
Change-Id: Iebd688ad8f4c08556846fcebb543e58bd2c01414
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions