From 2f7540e78f2a0952ddbbd9b953e186b90f401734 Mon Sep 17 00:00:00 2001 From: Mathias Agopian Date: Thu, 11 Mar 2010 15:06:54 -0800 Subject: implement connect/disconnect in our native_window_t implementations the framebuffer implementation doesn't do anything special with this but the surfaceflinger implementation makes sure the surface is not used by two APIs simultaneously. Change-Id: Id4ca8ef7093d68846abc2ac814327cc40a64b66b --- libs/ui/FramebufferNativeWindow.cpp | 2 ++ 1 file changed, 2 insertions(+) (limited to 'libs/ui/FramebufferNativeWindow.cpp') diff --git a/libs/ui/FramebufferNativeWindow.cpp b/libs/ui/FramebufferNativeWindow.cpp index 1fa2c68f2aa2..52380a077c7b 100644 --- a/libs/ui/FramebufferNativeWindow.cpp +++ b/libs/ui/FramebufferNativeWindow.cpp @@ -250,6 +250,8 @@ int FramebufferNativeWindow::perform(android_native_window_t* window, { switch (operation) { case NATIVE_WINDOW_SET_USAGE: + case NATIVE_WINDOW_CONNECT: + case NATIVE_WINDOW_DISCONNECT: break; default: return NAME_NOT_FOUND; -- cgit v1.2.3-59-g8ed1b