Because the window manager is responsible for organizing the screen, applications don't get to decide that. The window manager allocates surfaces and decides where they go and how they are layered; it never touches their bits, which is up to the application.
On Tue, Mar 17, 2009 at 3:21 PM, Videoguy <[email protected]> wrote: > > A surface is basically a pointer to block of memory. Why does a > separate process (i.e. Window Manager) have to create it? Why not the > activity itself create it? > > Does Window manager need access to that memory? > If so, why? > > Just curious. > > Thanks > Videoguy > > > > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
