Hi, Im currently trying to put together an idea of how WindowManagerService works - who it works with and how it works.
WindowManagerService is a system service - running in the system process I suppose. So it needs IPC to interact with applications. On the application side we have ViewRoot which is at the root of every window (activity) in an application. This has code to communicate with WindowManagerService via IWindowSession & IWindow. Something called WindowManagerImpl creates ViewRoots, so I suppose that WindowManagerImpl is executing in the application process. Is it kind of a proxy for for the WindowManagerService? App code can get a reference to WindowManagerImpl and thus get WindowManagerService to do things (via ViewRoot)? I presume there is one instance of WindowManagerImpl per app process. Something which is puzzling to me is that something called PhoneWindowManager makes calls directly on WindowManagerImpl, for instance when a new window is created, it calls WindowManagerImpl.addView() which ultimately results in a ViewRoot being crated which then notifies WindowManagerService about its existance. But PhoneWindowManager is created by WindowManagerService running in its own thread, in other words the system process... How can it make direct calls on WindowManagerImpl, if WindowManagerImpl is executing in applciation processes? Obviously I am sadly mistaken about one or more fundamental aspects or Android, but I am having a hard time tracking down any material to make things more clear. help!!!!!! cheeers --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
