On 12/04/16 12:27, Tom Hacohen wrote: > On 12/04/16 10:57, Carsten Haitzler wrote: >> just realized... Eo_Event *.... >> >> it has obj. shouldn't it ALSO have src too? for event propagation we >> really >> want to maintain src to be the original object the event happened on >> AND obj to >> be the event the callback is being called on... >> >> ... comments? >> >> > > Let me start by saying that the magic of the Eo_Event structure is that > we can add to it when we need to. Like now. :) > > At the moment we just overwrite obj (as you may know) and send a > "native" event. The problem I have with src is that I feel like it's > exposing internals of widgets for no apparent benefit. Having src feels > useful to me as well, but I don't have a usecase in mind. > > In cases where it's really needed, src could be added to the event info. > > -- > Tom.
Assuming it'll be needed for special events and not be needed in existing events. ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
