On Sun, 11 May 2008 06:59:29 +0200 (CEST) Vincent Torri <[EMAIL PROTECTED]>
babbled:
hmm. the pipe abstraction looks strange to me. why should i be limited to
writing just 1 void * down the pipe at a time. isn't the diea that i write
whatever i want (void *'s, int's, chars, whole arrays of ints or
Hey,
seems a good simple start - needs to be more complete, like actually close()ing
pips on delete - also i agree with peter, ecore_pipe_add and ecore_pipe_del -
also i would add ecore events for pipe data - like ecore_con, and pass the
WHOLE data read (not just 1 void* size element at a time)
On Fri, 25 Jan 2008 20:46:25 +0100 (CET) Vincent Torri <[EMAIL PROTECTED]>
babbled:
seems a good simple start - needs to be more complete, like actually close()ing
pips on delete - also i agree with peter, ecore_pipe_add and ecore_pipe_del -
also i would add ecore events for pipe data - like ecore
On Fri, 25 Jan 2008 20:46:25 +0100 (CET) Vincent Torri <[EMAIL PROTECTED]>
babbled:
seems a good simple start - needs to be more complete, like actually close()ing
pips on delete - also i agree with peter, ecore_pipe_add and ecore_pipe_del -
also i would add ecore events for pipe data - like ecore
Vincent Torri schrieb:
>
> Hey,
>
> as i have succedded in integrating the gstreamer thread in the ecore
> main loop on Windows, and as some of you talked about a pipe wrapper,
> I've quickly written a wrapper around pipe(), read() and write().
>
> I have attached the source file to put in ecore/
Hey,
as i have succedded in integrating the gstreamer thread in the ecore main
loop on Windows, and as some of you talked about a pipe wrapper, I've
quickly written a wrapper around pipe(), read() and write().
I have attached the source file to put in ecore/src/lib/ecore/ and a diff.
There
