summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator.cpp
diff options
context:
space:
mode:
authorJorim Jaggi <jjaggi@google.com>2015-12-22 16:29:16 +0100
committerJorim Jaggi <jjaggi@google.com>2016-01-05 13:49:23 +0100
commit0429f3522bca5bb86378dd3f013f995484ddbed6 (patch)
tree9687b4e71d961b0975873d031132b295bd0c2b79 /tools/aapt2/java/JavaClassGenerator.cpp
parentfe89d122e5b6b129b25d5d5316f690bd4ab93fbb (diff)
Freeze task bounds when relaunching
To make sure that task is only laid out with the size that matches the current configuration, we have to "freeze" the task bounds when we send a configuration change. Without this change, it could happen that the app already laid out with the new task bounds, but still had the old configuration, leading to wrong layouts. Bug: 26311778 Bug: 25015474 Change-Id: I8d3a3fdf3735f446a4affbbdb4986dafc97623a5
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator.cpp')
0 files changed, 0 insertions, 0 deletions