On 3/22/21 2:52 PM, Csaba Láng wrote:
Iohannes,
can you explain how I can send unicodepoints to text3d?
using the [string( message (see the [text3d] help-patch)
e.g. [string 67 115 97 98 97 32 76 225 110 103(
the problem is mainly that what comes out of [netreceive -b] is not
going to be unicode-points but utf-8 encodings thereof.
this is where the unicode-library i mentioned earlier comes into play.
something like:
[declare -path unicode]
[netreceive -b 9999]
[select 10 13]
| / [append $1(
| / [s $0-store]
| __/
|/ [r $0-store]
[list store]
|
[t a b]
| [s $0-store]
|
[route bang]
[utf82unicodenumber]
[list prepend string]
[list trim]
|
[text3d]
(the [s/r $0-store] is only to make the ascii-art nice; use proper
connections instead)
if you can use UDP instead of TCP, you can practically omit anything
between [select] and [route].
gfmadsr
IOhannes
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list
