<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Hello,
<br>
<br>
I already posted this to the forum, so I hope it's no foible to post
it here as well...
<br>
<br>
I am building a connector for PD to communicate with an external
application running on another system. I am using netsend to craft UDP
packets that the remote application can parse for actions. The payload
is supposed to look sort of like this:
<br>
(STRING,STRING,INTEGER,INTEGER,STRING,INTEGER)
<br>
<br>
Initially I was unable to get commas into the netsend stream because PD
uses commas as in internal delimiter. I was able to circumvent this by
using the cyclone external's 'sprintf' function. Like this:
<br>
<br>
|44|
<br>
|
<br>
|send (STRING%cSTRING%cINTEGER%cINTEGER%cSTRING%cINTEGER) |
<br>
|
<br>
<code class="moz-txt-verticalline"><span class="moz-txt-tag">|</span>netsend<span
class="moz-txt-tag">|</span></code>
<br>
<br>
this almost works, except that pd inserts whitespace characters after
the commas, which the remote application doesn't understand.
<br>
<br>
I noticed that 'print' actually puts a space before and after the
commas, whereas netsend (or sprintf) only puts one after the commas.
<br>
<br>
Does anyone know how to circumvent this behavior? Or, perhaps a simpler
way to achieve what I am trying to do?
<br>
<br>
Thank you.
<br>
<br>
Florian
<div class="moz-signature">-- <br>
<pre> :[ flo ]:
There is something you must understand about the Soviet system. They have the
ability to concentrate all their efforts on a given design, and develop all
components simulateously, but sometimes without proper testing. Then they end
up with a technological disaster like the Tu-144. In a technology race at
the time, that aircraft was two months ahead of the Concorde. Four Tu-144s
were built; two have crashed, and two are in museums. The Concorde has been
flying safely for over 10 years.
-- Victor Belenko, MiG-25 fighter pilot who defected in 1976
"Defense Electronics", Vol 20, No. 6, pg. 100
</pre>
</div>
</body>
</html>