[chuck-users] Flush ChucK IO

[mike clemow]

Hi Tom,

Colorful error message!

I'm afraid there's no socket communication in Chuck to my knowledge,
however, on Posix systems (and there my be an equivalent of this in Windows)
I've successfully used fifo pipes to communicate between a Chuck script and
another process.

Also, don't forget that you can send/receive OSC messages between processes
as well.  There my be a way to parse those in the process that runs your
visualization (especially if it's written in Java, C++, Python, or another
common language).  Often OSC is the best route, since it's implemented in so
many different environments.

Best,
Mike



2010/5/11 Tom Aizenberg <tom at tomaizenberg.nl>

>  Hi All,
>
>
>
> I am trying to make a visualization program for ChucK programs. For the
> communication between ChucK and the C++ code I’m writing, I use a pipe. I’d
> rather use a socket but I cannot see how this works in ChucK (?).
>
>
>
> When I write to *chout* I need to flush the buffer, just to read in the
> output using my own program. When I try to do this (i.e.
> my_IO_object.flush()) I get the following message:
>
>
>
> *“(IO): internal error! inside an abstract function! help!*
>
> *    note: please hunt down someone (e.g., Ge) to fix this...”*
>
>
>
> The command I use is: *chuck-1.2.1.3-exe\bin\chuck.exe
> chuckVis\chuckFiles\random1.ck*, on Windows Vista 32-bits. Without the
> .flush() the script works fine, but I need the flush functionality…
>
>
>
> Has anybody got a clue how to fix this? Or maybe how to use ChucK to send
> messages through a socket?
>
>
>
> Greetings,
>
>
>
> Tom Aizenberg
>
> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
>
>


-- 
http://michaelclemow.com
http://semiotech.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cs.princeton.edu/pipermail/chuck-users/attachments/20100511/85244cf0/attachment.html>