>> It is anticipated that most of the time, the GUI will be started
>> by the LADSPA host in response to some user action.
>
>I'd like to be able to use a text mode interface, controlling
>two or more ports (maybe on different plugins) from one program
>using the keyboard.
Its not directly on ta
David Riley <[EMAIL PROTECTED]> writes:
> http://www.dmriley.demon.co.uk/tmp/lcp-perl.0.03.tar.gz
s/03/04/
read() now working.
--
David Riley [EMAIL PROTECTED]
Paul Davis <[EMAIL PROTECTED]> writes:
> It is anticipated that most of the time, the GUI will be started
> by the LADSPA host in response to some user action.
I'd like to be able to use a text mode interface, controlling
two or more ports (maybe on different plugins) from one program
using the
>> in this release, its no longer necessary for clients to handle
>> "changed" messages from the LCP host if they don't want to.
>
>U. Sorry, I can't keep up with everything on this list. If you
>make an announcement like this it would be really nice to have a couple
>of lines explaining what
On Wed, 19 Dec 2001 22:46:37 -0500
Paul Davis <[EMAIL PROTECTED]> wrote:
> in this release, its no longer necessary for clients to handle
> "changed" messages from the LCP host if they don't want to.
U. Sorry, I can't keep up with everything on this list. If you
make an announcement like th
oops, url:
http://www.op.net/~pbd/lcp-0.2.0.tar.gz
in this release, its no longer necessary for clients to handle
"changed" messages from the LCP host if they don't want to. in earlier
versions, not handling this would cause problems with pipe data
overflows, blocking behaviour, etc. in 0.2.0, if the client
does not register a "changed" callback w
