On Wed, 14 Sep 2011 10:25:59 -0400 Mike Blumenkrantz
wrote:
> On Sun, 11 Sep 2011 21:53:11 +1000
> David Seikel wrote:
>
> > From my reading of the ecore fd handler code, returning
> > ECORE_CALLBACK_CANCEL from the handlers callback does the same as
> > ecore_main_fd_handler_del(), which is to
On Mon, 12 Sep 2011 05:08:27 +1000
David Seikel wrote:
> On Sun, 11 Sep 2011 21:53:11 +1000 David Seikel
> wrote:
>
> > From my reading of the ecore fd handler code, returning
> > ECORE_CALLBACK_CANCEL from the handlers callback does the same as
> > ecore_main_fd_handler_del(), which is to mark
On Sun, 11 Sep 2011 21:53:11 +1000
David Seikel wrote:
> From my reading of the ecore fd handler code, returning
> ECORE_CALLBACK_CANCEL from the handlers callback does the same as
> ecore_main_fd_handler_del(), which is to mark the handler for deletion,
> not actually do the deletion. The delet
On Sun, 11 Sep 2011 21:53:11 +1000 David Seikel
wrote:
> From my reading of the ecore fd handler code, returning
> ECORE_CALLBACK_CANCEL from the handlers callback does the same as
> ecore_main_fd_handler_del(), which is to mark the handler for
> deletion, not actually do the deletion. The delet
From my reading of the ecore fd handler code, returning
ECORE_CALLBACK_CANCEL from the handlers callback does the same as
ecore_main_fd_handler_del(), which is to mark the handler for deletion,
not actually do the deletion. The deletion actually happens at some
later point. So it seems to be safe
