Re: [E-devel] ECORE_CALLBACK_KEEP and ECORE_CALLBACK_REMOVE

2008-01-07 Thread Nathan Ingersoll
That would be reasonable as well, as long as it clearly indicates that it prevents or allows the callback from recurring. On Jan 7, 2008 6:12 PM, Michael Jennings <[EMAIL PROTECTED]> wrote: > On Tuesday, 08 January 2008, at 00:59:22 (+0100), > Peter Wehrfritz wrote: > > > > I want to add two alias

Re: [E-devel] ECORE_CALLBACK_KEEP and ECORE_CALLBACK_REMOVE

2008-01-07 Thread Michael Jennings
On Tuesday, 08 January 2008, at 00:59:22 (+0100), Peter Wehrfritz wrote: > > I want to add two aliases (ECORE_CALLBACK_KEEP and > > ECORE_CALLBACK_REMOVE) to Ecore.h. They can be used as return > > values for the ecore callbacks like timer, idler etc. Imho that > > improves code-readability and he

Re: [E-devel] ECORE_CALLBACK_KEEP and ECORE_CALLBACK_REMOVE

2008-01-07 Thread Peter Wehrfritz
Peter Wehrfritz schrieb: > Hi all, > > I want to add two aliases (ECORE_CALLBACK_KEEP and > ECORE_CALLBACK_REMOVE) to Ecore.h. They can be used as return values > for the ecore callbacks like timer, idler etc. Imho that improves > code-readability and helps (at least me) to write code, because y

[E-devel] ECORE_CALLBACK_KEEP and ECORE_CALLBACK_REMOVE

2008-01-05 Thread Peter Wehrfritz
Hi all, I want to add two aliases (ECORE_CALLBACK_KEEP and ECORE_CALLBACK_REMOVE) to Ecore.h. They can be used as return values for the ecore callbacks like timer, idler etc. Imho that improves code-readability and helps (at least me) to write code, because you don't have to remember if 0 sto