Hi,<br><br>thanks for the reply..<br><br>the osc function addString ... thinking about that now i have no idea why i didn't just try that.. :-/<br>sometimes i wonder how stupid one (me) can be :-)<br><br><span class="q">>> another question is about System Information from within chuck..
<br>>> are there functions<br>>> that for example return information about all available midi ports<br>>> - as a list, an array or<br>>> something similar? (like the VM option --probe)<br><br></span>
<div style="direction: ltr;">>Not currently, no, although something like that would be good to have.</div><br>yes that would really be good.. also a function that reports the running shreds the same way.<br><br><br>> I think one hack-y option would be to parse the output of chuck --
<br>> probe directly in your UI. But ultimately it would be nice to be<br>> able to access that information in ChucK directly.<br><br>yes i thought about that but yet i didn't get this to work correct.. seems to be a common
<br>problem (maybe only windows?) that some of the output can only be read when <br>the concole app exits.. i will see..<br><br><br>thanks<br>-tz<br><br><br><br><div><span class="gmail_quote">2006/12/8, Spencer Salazar <
<a href="mailto:ssalazar@cs.princeton.edu">ssalazar@cs.princeton.edu</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Tazumi,
<br><br>On Dec 8, 2006, at 7:42 AM, tazumi wrote:<br><br>> Hi List,<br>><br>> hello to everybody.. i am new to this list..<br>><br>> i have got a question about sending strings with the osc class..<br>> ist this possible?
<br>> The manual says that the osc object has 2 member functions<br>> (addInt / addFloat)..<br>> so is there a way to send (or revieve) other data types?<br><br>It seems the manual is out of date in this regard, it is in fact
<br>possible to send strings in ChucK's OSC implementation. Just use an<br>"s" for the type specifier and addString to supply the string.<br>getString will retrieve the string on the listener end.<br><br>> another question is about System Information from within chuck..
<br>> are there functions<br>> that for example return information about all available midi ports<br>> - as a list, an array or<br>> something similar? (like the VM option --probe)<br><br>Not currently, no, although something like that would be good to have.
<br><br>> Currently i am working on a kind of chuck user interface.. i want<br>> the UI and chuck to<br>> communicate over OSC - so a way to get Information about the<br>> current Environment<br>> (from within chuck and send them to the UI) would really be great...
<br><br>I think one hack-y option would be to parse the output of chuck --<br>probe directly in your UI. But ultimately it would be nice to be<br>able to access that information in ChucK directly.<br><br>spencer<br><br>>
<br>> thanks<br>><br>> -- tazumi<br>> _______________________________________________<br>> chuck-users mailing list<br>> <a href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu
</a><br>> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br><br>_______________________________________________<br>chuck-users mailing list
<br><a href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</a><br><a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
</a><br></blockquote></div><br><br clear="all"><br>-- <br>tazumi<br>