Hello Haitao! You might have a better chance getting an answer to the email below on the MTF mailing list. On CC and Reply-To set.
On Do, 2010-10-21 at 11:29 +0100, Feng, Haitao wrote: > Dear mcompositor developers, > > Yongsheng and I have a question on mcompositor, why does the compositing > functionality depend on the type of the topmost window? > > The function MCompositeManagerPrivate::possiblyUnredirectTopmostWindow() will > judge whether the topmost root window isAppWindow(true), if it is true, it > will > not do the compositing. Otherwise it will do the compositing which means it > will > get the texture of the topmost window, combine the decorator texture and draw > them into full screen on mcompositor's GL window. > > Comparing the below two alternative coding logics: > 1. If it is AppWindow, draw the AppWindow's texture on compositor's GL > window. This means mcompositor's GL window will be always mapped. > 2. If it is not AppWindow, combine it with decorator directly and do not > touch > texture staff. This means mcompositor is only used for window animation. > > Is there any special consideration on this design logic? > > Thanks > -Haitao > _______________________________________________ > MeeGo-dev mailing list > MeeGo-dev@meego.com > http://lists.meego.com/listinfo/meego-dev -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
