diff options
| author | Evan Laird <evanlaird@google.com> | 2017-06-13 15:09:21 -0400 |
|---|---|---|
| committer | Evan Laird <evanlaird@google.com> | 2017-06-13 15:09:21 -0400 |
| commit | 418ffe4a0feeeff3e29b3852bc37b3092f4c864a (patch) | |
| tree | c648541a1349a79a03c275e52a9bf24a49ce8cbb /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | 5148d9fe8153da418dfe58919043e8daf1df195d (diff) | |
Change SlashDrawable semantics to fix QS crash
SlashDrawable wraps a reference to Drawable in order to store the
intended Drawable and optionally draw a slash over it. As such, it
should probably have similar semantics to Drawable, in that it either
exists or doesn't; if you set SlashImageView's drawable to `null`, you'd
expect that the drawable goes away, not that the SlashDrawable's
contained Drawable goes away but the slash stays.
Test: runtest systemui
Change-Id: I34b92716cc60ba5043ab68ae09954f5a5e97e562
Fixes: 62525439
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions