3c5d125ed7
This factors out the boiler-plate code from the sample app to a common glue code that can be used for everyone writing this style of app: a dedicated app thread that takes care of waiting for events and processing them. As part of doing this, ALooper has a new facility to allow registration of fds that cause ALooper_pollOnce() to return the fd that has data, allowing the app to drive the loop without callbacks. Hopefully this makes some people feel better. :) Also do some other cleanup of the ALooper API, plus some actual documentation. Change-Id: Ic53bd56bdf627e3ba28a3c093faa06a92be522b8 |
||
|---|---|---|
| .. | ||
| tests | ||
| Android.mk | ||
| EGLUtils.cpp | ||
| EventHub.cpp | ||
| EventRecurrence.cpp | ||
| FramebufferNativeWindow.cpp | ||
| GraphicBuffer.cpp | ||
| GraphicBufferAllocator.cpp | ||
| GraphicBufferMapper.cpp | ||
| Input.cpp | ||
| InputDispatcher.cpp | ||
| InputManager.cpp | ||
| InputReader.cpp | ||
| InputTransport.cpp | ||
| IOverlay.cpp | ||
| KeyCharacterMap.cpp | ||
| KeyLayoutMap.cpp | ||
| KeyLayoutMap.h | ||
| MODULE_LICENSE_APACHE2 | ||
| NOTICE | ||
| Overlay.cpp | ||
| PixelFormat.cpp | ||
| Rect.cpp | ||
| Region.cpp | ||