Thank you all so much!<br>Building the filename and passing it onto an [ open $1 ( message worked perfectly.<br>One should know better by now, I should've thought of it... oh well. Hindsight is 20/20.<br>Cheers<br><br>
<div class="gmail_quote">On Sun, Feb 21, 2010 at 6:41 PM, Jonathan Wilkes <span dir="ltr"><<a href="mailto:jancsika@yahoo.com">jancsika@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
--- On Sun, 2/21/10, Roman Haefeli <<a href="mailto:reduzierer@yahoo.de">reduzierer@yahoo.de</a>> wrote:<br>
<br>
> From: Roman Haefeli <<a href="mailto:reduzierer@yahoo.de">reduzierer@yahoo.de</a>><br>
> Subject: Re: [PD] turn a symbol to a message<br>
> To: "Ignacio Lois" <<a href="mailto:ignaciolois@gmail.com">ignaciolois@gmail.com</a>><br>
> Cc: <a href="mailto:pd-list@iem.at">pd-list@iem.at</a><br>
> Date: Sunday, February 21, 2010, 11:03 AM<br>
<div><div></div><div class="h5">> On Sat, 2010-02-20 at 20:01 +0100,<br>
> Ignacio Lois wrote:<br>
> > Hello everyone.<br>
> ><br>
> > I've been pulling my hair out for a while with an<br>
> inexplicable<br>
> > problem.<br>
> > I'm trying to build an [open file.wav( message to feed<br>
> a [readsf~]<br>
> > object.<br>
> > A [makefilename] object is returning the exact symbol.<br>
> I'm connecting<br>
> > it to a [$1( message, and then onto the [readsf~]<br>
> object and I get the<br>
> > error: "readsf~_ no method for 'open file.wav'<br>
> > If I replace the $1 message for the hard coded "open<br>
> file.wav", it<br>
> > works perfectly.<br>
> > What am I doing wrong?<br>
><br>
> And yeah: Pd is missing a way to display the distinction<br>
> between:<br>
><br>
> "'open file.wav'" <-<br>
> 'open file.wav' selector<br>
><br>
> and:<br>
><br>
> "'open' 'file.wav'" <- message with 'open'<br>
> selector<br>
> <br>
> and 'file.wav' as first<br>
> argument<br>
><br>
> Both look the same, when printed. This indeed could be<br>
> confusing. How<br>
> about adding a 'debug' [print] option (-d?) to make [print]<br>
> not decode<br>
> incoming message, but make it print all the implicit stuff,<br>
> that is<br>
> usually hidden? Would that make sense?<br>
<br>
</div></div>How would [print] resolve this ambiguity? Both messages above<br>
are handled by the print_anything method, which prints the selector<br>
+ any atoms that make up the rest of the message. Plus if there's a way<br>
to clearly distinguish visually between these two messages, I'd rather see<br>
that solution applied to Pd as a whole, so that for instance symbols with<br>
spaces in them may be saved in a patch.<br>
<br>
In the meantime, it might be helpful to make an abstraction that breaks up<br>
an incoming message into its constituent parts. So one's output would look like this:<br>
selector: open file.wav<br>
arguments:<br>
<br>
while the the other's would look like this:<br>
selector: open<br>
arguments: file.wav<br>
<br>
But I don't think this should be the job of the [print] object.<br>
<font color="#888888"><br>
-Jonathan<br>
<br>
<br>
<br>
<br>
</font></blockquote></div><br>