Carsten Haitzler <[EMAIL PROTECTED]> [2005-03-28 08:41]: > On Mon, 28 Mar 2005 00:14:00 +0200 Tilman Sauerbeck <[EMAIL PROTECTED]> > babbled: > > > Hi, > > I was missing a "prepare" callback in Ecore's FD handler - a callback > > that's executed just before the main loop actually checks for the file > > descriptors' states. One use of this prepare callback is that you can > > change the state the FD handler should check for. > > > i'm wondering to see if you need it? why do you need it? there's 2 callbacks > for > fd's, one for raw fd data and one for buffered data (ie xlib buffers data so > there may be data available in the xlib internal buffer like events, but the > fd > is not actually active for reading - this is why i added this - i am wondering > if you are just re-implementing the buffered data callback in a different > way???)
The example I gave is what I need this for; I need a flexible Ecore_Fd_Handler - I need to set the flags the FD handler should check for just before it actually checks for them. So in that prepare callback I'd call ecore_fd_handler_active_set(). This could also be done with an FD handler and a timer, that periodically sets the flags on the FD handler, but that's pretty ugly and not reliable. So no, it cannot be done with the buffer callback :) -- Regards, Tilman ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
