92e08bf997bcd1459df4d2efe9fd51993908dd3e
If BLAST is enabled and we somehow end up in positionLost or setParentSpaceRectangle without having called setUseBLASTSyncTransaction we will end up putting operations in to a Transaction which will never be applied. This condition should be considered a bug, but it's best to defend against it. To compensate, rather than checking the global use BLAST flag, we check if the current draw is actually using BLAST. Bug: 152663327 Bug: 152780239 Test: Existing tests pass Change-Id: I3c05b83400b59be82a339933fc8ef1382d4f0e21
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%