Hi, please don't change the behavior of existing public APIs (in this case the display parameter, which right now is not used, and should not be used except for official platform changes). You should add your own APIs to do the things you want, ideally as a separate shared library as shown by the PlatformLibrary sample code.
On Thu, Dec 24, 2009 at 5:55 PM, hongxue.ren <bigc...@gmail.com> wrote: > Hi, all > I am working on android multi screens. > Now, the emulator can support two screens simultaneously, and the > following work is based on it. > I modified some native code in directory surfaceflinger and ui, and > also some java code about WindowManager, > ViewRoot etc. > > I use the second screen with the code follow: > lp.setDisplay(1); > mWindowManager.addView(view, lp); > And the 'lp' is WindowManager.LayoutParams type. I add a new method > setDisplay() to Class WindowManager.LayoutParams. > > Now, the secondary screen only can show the view when the activity run > in the first time(it means onCreate() is called). > when the activity is switched back, and the view is shown on the first > screen. > > Anyone is working on the multi screen, we can > > > > > > -- > unsubscribe: > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > website: http://groups.google.com/group/android-porting > -- 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. -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
