5f555569e7
This isn't really right either, but avoids having an extra buffer that the consumer has to drain which it might not be expecting. To be correct, disconnecting a surface from a context should retain the current buffer and continue using it when reconnected. The buffer should only be canceled when the surface is destroyed. That will wait for a later change. Bug: 8320762 Change-Id: I5efa39c741193ca4f5612ea9de001ccbb683b345 |
||
---|---|---|
.. | ||
Android.mk | ||
array.cpp | ||
array.h | ||
BufferObjectManager.cpp | ||
BufferObjectManager.h | ||
context.h | ||
dxt.cpp | ||
dxt.h | ||
egl.cpp | ||
fixed_asm.S | ||
fp.cpp | ||
fp.h | ||
iterators.S | ||
light.cpp | ||
light.h | ||
matrix.cpp | ||
matrix.h | ||
mipmap.cpp | ||
primitives.cpp | ||
primitives.h | ||
state.cpp | ||
state.h | ||
texture.cpp | ||
texture.h | ||
TextureObjectManager.cpp | ||
TextureObjectManager.h | ||
Tokenizer.cpp | ||
Tokenizer.h | ||
TokenManager.cpp | ||
TokenManager.h | ||
vertex.cpp | ||
vertex.h |