diff options
| author | 2025-03-18 20:39:19 +0900 | |
|---|---|---|
| committer | 2025-03-18 09:28:29 -0700 | |
| commit | 80e83f7238d3a18a21946a7919817beeb99f7b29 (patch) | |
| tree | 73e53fe366934a6718a91e52c3c729d591e93b4b /libs/androidfw/AssetsProvider.cpp | |
| parent | dd8f4e6bbc8f5743d807d6ef146889c47e1a44e5 (diff) | |
Update DisplayLayout#mGlobalBoundsDp when display config changes
Previously, when `DisplayController#onDisplayConfigurationChanged` was
called, a new `DisplayLayout` was created, but its `globalBoundsDp`
field was not updated to reflect the topology. This field was
initialized with dimensions based on the display size.
The drag indicator rendering logic uses `globalBoundsDp` to determine
whether the dragged window overlaps the display. Since `globalBoundsDp`
was incorrect after a configuration change, the indicator was always
rendered, even if the window was not actually over the display.
This change updates `onDisplayConfigurationChanged` to set the
`globalBoundsDp` of the new `DisplayLayout` using the `DisplayTopology`
Bug: 398842461
Test: Manual test; atest WMShellUnitTests:DisplayControllerTests
Flag: com.android.window.flags.enable_connected_displays_window_drag
Change-Id: I2a8eb66e2615a87e62d87bafeb9821275aa41638
Diffstat (limited to 'libs/androidfw/AssetsProvider.cpp')
0 files changed, 0 insertions, 0 deletions