See the message : http://sourceforge.net/mailarchive/forum.php?thread_name=c81c5d9c1002270545s70e25e53wbddded2772c6b...@mail.gmail.com&forum_name=enlightenment-devel
2010/3/7 Carsten Haitzler <ras...@rasterman.com> > On Fri, 26 Feb 2010 13:11:03 +0800 Brian Wang <brian.wang.0...@gmail.com> > said: > > > Hello all, > > > > I've been bothered by this question for quite some time but still > > haven't been able to come up with a simple code that reproduce the > > problem. > > > > Here it goes: > > elm_notify container may be mis-positioned after some objects are > > created and destroyed later. By 'mis-positioned', I mean that if the > > style is set to 'top', the elm_notify object may appear in a 'non-top' > > place. > > >It seems as it's getting the geometry of its parent (elm_win) wrong. > > this shouldnt happen - the onyl way those other objects would affect notify > is > with a parent/child relationship being modified (ie a parent is having its > sizing modified by other widgets and their properties) > > > I see a similar problem with elm_hover. > > This problem is definitely reproducable every time. However, I have > > yet to trim down the code to make it happen. > > never seen this... ever... a test case would be good. > > > I'm not sure if it's related to my code sequence. By observation, it > > seems to be somehow related to elm_win_resize_object_add(). > > well if u add an obj as a resize obj AND its a child of some other > widget... u > are in trouble. are you doing that? > > > Any hints? (Yes, I know the description of the problem is somehow > vague...) > > Again, thanks in advance. :-) > > > > > > brian > > > > > > -- > > brian > > ------------------ > > > > Cool-Karaoke - The smallest recording studio, in your palm, open-sourced > > http://cool-idea.com.tw/ > > > > iMaGiNaTiOn iS mOrE iMpOrTaNt tHaN kNoWlEdGe > > > > > ------------------------------------------------------------------------------ > > Download Intel® Parallel Studio Eval > > Try the new software tools for yourself. Speed compiling, find bugs > > proactively, and fine-tune applications for parallel performance. > > See why Intel Parallel Studio got high marks during beta. > > http://p.sf.net/sfu/intel-sw-dev > > _______________________________________________ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > The Rasterman (Carsten Haitzler) ras...@rasterman.com > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Regards. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
