> > I believe we should always return Etk_Bool in all callbacks and stop > > the emission when returning 0 (FALSE). > > +1
Done in CVS. I've also commited many improvements in Etk signal system. Mainly now instead of having one big list for every callback, each object has an array of callbacks. So when a signal is emitted, you don't need to filter the big list. Etk_Signal_Callback don't have a pointer to signal anymore, this helps to even out the memory requirements for the having the array. Also incorporated another patch I sent to the mailing list regarding disconnecting (and blocking, and unblocking) unique signal_callbacks by passing an identifier (Etk_Signal_Callback *) or passing the Callback and the original data pointer. Review on these is appreciated, thanks for all help. PS: Next week I'll update Python-Etk. Cheers, Caio Marcelo ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
