On 13/10/11 14:11, Carsten Haitzler (The Rasterman) wrote: > well here's my take. > > signals are a generic abstract way to talk with edje. it literally allows edje > to even have the whole engine run in another process/thread and handle signals > off there. the design allows it so in future we could take advantage of that. > but this create complications - like anything (x is a good example as its also > async). you could ADD smart callbacks for the edje signals and transition to > use those instead within elm_entry. i think this is probably ok. >
So should I revert my signal related patches and move to smart callbacks then? As I said, my biggest problem is that now signals and callbacks will be "out of order" i.e not in the order expected, are you find with that? -- Tom. ------------------------------------------------------------------------------ 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
