Thanks for reply. Now I have a requirement that seems need breaking the normal workflow of "drawing-->compose" strategy. As I know, each window(ViewRoot) itself draw its whole view hierarchy to the surface(unlockCanvasAndPost()) actually allocated by WindowManagerService. Then the WindowManagerService use Surface.show() to invoke surfaceflinger to compose it with other window's surfaces. The whole strategy seems fixed. For example, when the surface is composing, how to compose them, is already determined by WindowManagerService and SurfaceFlinger etc. But I hope I can customize this work flow, for example: 1. Activity draw to Surface A and post 2. Before Surface A show(), the customized WindowManager create another surface B, then privately do some compose operation, this compose operation is different than surfaceflinger do for everyone, the composing dst is Surface B rather than display screen 3. Then WindowManager really show Surface B, the Surface A is never be shown on screen.
May you help me that is there any method can do it except hack for surface flinger or current windowmananger service etc. Thanks Regards On Oct 20, 12:42 pm, Dianne Hackborn <hack...@android.com> wrote: > Not at all. > > On Mon, Oct 19, 2009 at 7:45 PM, Westermann Fu <westerman...@gmail.com>wrote: > > > Dear All: > > > Can the WindwoManagerService be replaced dynamicly in run time? The reason > > I ask for it is that I want to do something when any window appear on top of > > window stack, or when it appears on screen, such as I can dynamicly add a > > SurfaceView on it (The window is not created by me, it may be any window > > currently exist or may be created in furture), and when it disappears I can > > delete it. I think that I must customize the window manager service for > > doing it, but can I make the result as an .apk file to install on mobile > > device when published? Thanks. > > > Regards > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. 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 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 -~----------~----~----~----~------~----~------~--~---
