On Thu, 16 Sep 2010 18:08:52 -0300 Gustavo Sverzut Barbieri <[email protected]> said:
> On Thu, Sep 16, 2010 at 5:23 PM, Carsten Haitzler <[email protected]> > wrote: > > On Thu, 16 Sep 2010 14:04:00 -0300 Gustavo Sverzut Barbieri > > <[email protected]> said: > > > >> 2010/9/16 Tiago Falcão <[email protected]>: > >> > Hi, > >> > > >> > Tooltips and others features need listen mouse events of widgets. But > >> > don't work with elm_scroller based widgets. > >> > > >> > Elm_Scroller is composed by Els_Scroller and one content. But is > >> > Els_Scroller that receive mouse events and it disable events propagation > >> > in els_scroller.c:2312. > >> > > >> > Disabling this line enables mouse_events in elm_scroller based widgets. > >> > And tooltips works in scrolled_entry. > >> > Now we need one fix. I don't know the better solution. > >> > > >> > What kind of problems we would have to remove that line? Others ideas? > >> > >> I think it does make sense to propagate the events there, otherwise > >> the elm_smart_scroller->event_obj will not forward its mouse events to > >> the parent and so any mouse events on elm_smart_scroller (and thus > >> elm_scroller) is ignored. > >> > >> Raster, any particular reason you forced to not propagate? > > > > i don't remember... but i'm sure there is. > > 2 approaches there: > > - raster approach: change, commit, let people report. In our tests, > it did not change a thing. > - philosopher approach: think about it and come to us later, but > give it a timeline otherwise cursor and tooltips are broken. i don't have time for #2 :) > Note that we do know a work around: the objects that have an > els_scroller inside could create its own event_obj on top, set to > propagate events and repeat events, then it will work... but it is a > hack that will easily spread all over the code :-/ > > as a hint trying to figure out why you have that: maybe if the child > gets the events, and is set to propagate, then you have the event > reported to parent twice? Once per child? If that is the case, it > would be better to set no-propagate on the child, not the event_area > (as we guarantee event_area always get events, while the child may or > may not)? > > > -- > Gustavo Sverzut Barbieri > http://profusion.mobi embedded systems > -------------------------------------- > MSN: [email protected] > Skype: gsbarbieri > Mobile: +55 (19) 9225-2202 > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
