Probably that's a better solution. Curly braces aren't the only problem Pd has with JSON format strings: they contain spaces and commas, which will result in them being split into separate messages.
Martin
On 2012-01-11 12:42, Hans-Christoph Steiner wrote:
Or perhaps purestjson would help here: https://github.com/residuum/PuRestJson
.hc
On Jan 11, 2012, at 9:04 AM, Martin Peach wrote:
I guess you could use another pair of characters to represent curly brackets and intercept them as they pass between [packOSC] and [udpsend], replacing them with the codes (123 and 125) for curly brackets. (The output of [packOSC] is a list of ASCII character codes).
Martin
On 2012-01-11 03:16, Scott R. Looney wrote:
hi folks- being new to PD i just discovered this rather curious inability to form any kind of message using a Curly brace - { or }. luckily the GUI doesn't crash like before but it refuses to type the characters. can someone update me on whether that will be addressed anytime soon, or if not, explain how i could send a statement containing these characters to udpsend via packOSC? i guess i don't have to see them or print them but they at least have to be sent.
this is sort of important to anyone wanting to address dynamic interface creation via JSON as shown by Charlie Roberts in this Max MSP example:
http://charlie-roberts.com/Control/?p=292
Control is the completely open source variant of closed source projects like TouchOSC and is much more extendable, as it's completely based on HTML5, CSS and JSON. i'm currently in the process of porting his demo patch of dynamic interface creation he made up to PD from Max.
anyway if anyone has some answers i'd appreciate it - thanks in advance!
scott
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
“We must become the change we want to see. - Mahatma Gandhi