[PD] OSC data from [list trim]

[Mitchell Turner]

Roman,
Yes, I’m sorry I was not more clear. I should have begun the thread with: I’m receiving OSC messages in Pd from the iPhone app, TouchOSC.

I think my fundamental misunderstanding was that the first item in the list is a symbol. It looked like a float, so I thought it was a float.

Thanks for your help,
Mitch

    

> On Jul 13, 2019, at 2:48 PM, pd-list-request at lists.iem.at wrote:
> 
> Message: 1
> Date: Sat, 13 Jul 2019 19:49:50 +0200
> From: Roman Haefeli <reduzent at gmail.com <mailto:reduzent at gmail.com>>
> To: Christof Ressi <christof.ressi at gmx.at <mailto:christof.ressi at gmx.at>>, Pd-List
> 	<pd-list at lists.iem.at <mailto:pd-list at lists.iem.at>>,  Miller Puckette <msp at ucsd.edu <mailto:msp at ucsd.edu>>
> Subject: Re: [PD] OSC data from [list trim]
> Message-ID: <533a1ea1c3c68ca7b7ab00d2c24061a49e19d86c.camel at gmail.com <mailto:533a1ea1c3c68ca7b7ab00d2c24061a49e19d86c.camel at gmail.com>>
> Content-Type: text/plain; charset="utf-8"
> 
> On Sat, 2019-07-13 at 18:46 +0200, Christof Ressi wrote:
>> I think the problem lies somewhere else. There is a fundamental issue
>> with [oscparse]: it breaks the address pattern into its parts and
>> forms a Pd list, but treats numbers as symbols. 
> 
> Ah, thanks for pointing this out. From the original post it was (at
> least for me) not quite clear whether it was about the OSC atoms (the
> actual payload) or the OSC path. 
> 
> Good to know that numeric path elements end up (actually: are
> preserved) as symbols in Pd after [oscparse].
> 
> Roman

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20190713/9923c1d2/attachment.html>