For Csound5, I think your idea is best. Csound internally should not poll.
But I don't know the code well enough to say that nothing will break if
POLL is removed.

Clients could either poll in a separate thread, or they could render one
ksmps at a time and then poll in the same thread.

Original Message:
-----------------
From:  jpff@codemist.co.uk
Date: Mon,  8 Dec 2003 09:21:32 +0000
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3709] POLLing in Csound5


It seems to me that the API means that there should be no reason to
poll the interface from inside csound, and this would be left to the
user interface, probably running on a separate thread.  Is this
really the case?  Can I remove all POLL_EVENTS code?  It would simplify
a great deal.

Also, in a similar vein, winX11 winFLTK etc should be removed.  Any
thoughts?

I now have a csound5 compiling on OSX, but not tested.

==John ffitch


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .