Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

get rid off unneeded flags

Browse Source
This commit is contained in:
Mathias Agopian
2009-05-05 18:29:35 -07:00
parent b51e18d59b
commit 9bd5da4db9
2 changed files with 3 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
libs/ui/FramebufferNativeWindow.cpp
View File

@@ -110,28 +110,7 @@ FramebufferNativeWindow::FramebufferNativeWindow()
fbDev->width, fbDev->height, strerror(-err));
}
uint32_t flags = fbDev->flags & SURFACE_FLAG_MAPPED;
/*
* FIXME: SURFACE_FLAG_PRESERVE_CONTENT
* how to implement this, there is no concept of preserve content in
* the framebuffer, which just "posts" buffer.
*
* It looks like what we need is a way to know if the posted buffer can
* be reused. But if so, why allocating 2 buffers?...
*
* should the lock/unlock calls take care of the copy-back?
*
*
* In the end, the client wants to know if the backbuffer is preserved
* though... it's complicated.
*
*/
//flags |= SURFACE_FLAG_PRESERVE_CONTENT;
const_cast<uint32_t&>(android_native_window_t::flags) = flags;
const_cast<uint32_t&>(android_native_window_t::flags) = fbDev->flags;
const_cast<float&>(android_native_window_t::xdpi) = fbDev->xdpi;
const_cast<float&>(android_native_window_t::ydpi) = fbDev->ydpi;
const_cast<int&>(android_native_window_t::minSwapInterval) =