On Fri, 14 Oct 2011 11:08:16 +0000 (GMT) EunMi Lee <eunmi15....@samsung.com>
said:

> Thank you for your explaination :)
> I understand why scroller always gets event firstly.
> so,
> evas_object_propagate_events_set(scroller's content obj, EINA_FALSE)
> and
> event_flags |= EVAS_EVENT_FLAG_ON_HOLD in the scroller's content obj
> will not work! I'm sorry about that T_T
> I have to find other solution to stop scroller.

can you explain in detail what you are trying to do? elm does this kind of
thing when you put a scroller inside a scroller...

> ------- Original Message -------
> Sender : Carsten Haitzler<ras...@rasterman.com>
> Date : 2011-10-14 19:10 (GMT+09:00)
> Title : Re: [E-devel] Question about event propagation routine of elm_scroller
> 
> On Thu, 13 Oct 2011 02:19:09 +0000 (GMT) EunMi Lee 
> said:
> 
> aaaah. this is actually an interesting one. evas has some cool mechanisms that
> are used to make events reroute all over the place. what scroller does is this
> in objects stacking:
> 
> =============< scroller
> --- --- - --< objects under scroller
> 
> the scroller has an invisible rectangle that "repeats" events (repeat ==
> object on top gets event then repeats the events to the next object down
> until either no object exists or some object swallows the event without
> repeating). so the event goes FIRST (in order of object stacking from top to
> bottom) to the scroller, then drops through to objects below (inside the
> scroller)
> 
> > Hello all,
> > 
> > I have a question about event propagation routine among Evas_Object
> > specially elm_scroller. I made an application which has Evas_Objects as
> > follows: my object -> elm_layout -> elm_box -> elm_scroller -> elm_navibar
> > ("->" means : left is contained to right) I expect that event is propagated
> > from child to parent, but event propagation routine is as follows:
> > elm_scroller -> elm_navibar -> my object -> elm_layout -> elm_box ("->"
> > means : left object gets event early)
> > 
> > Why elm_scroller always get event firstly even though it has child?
> > I want to not propagate event to the elm_scroller using
> > EVAS_EVENT_FLAG_ON_HOLD if my object consumes event. but I can not do that
> > because elm_scroller gets event earlier than my object. If elm_scroller's
> > event routine is correct, is there any other solution? (additional
> > information: my object is not an elementary widget. it is just an
> > Evas_Object.)
> > 
> > Regards,
> > Eunmi Lee
> > ------------------------------------------------------------------------------
> > All the data continuously generated in your IT infrastructure contains a
> > definitive record of customers, application performance, security
> > threats, fraudulent activity and more. Splunk takes this data and makes
> > sense of it. Business sense. IT sense. Common sense.
> > http://p.sf.net/sfu/splunk-d2d-oct
> > _______________________________________________
> > 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

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    ras...@rasterman.com


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to