[PD] "get" method for Pd
jancsika at yahoo.com
Thu Nov 17 22:54:36 CET 2011
----- Original Message -----
> From: Mike Moser-Booth <mmoserbooth at gmail.com>
> To: Jonathan Wilkes <jancsika at yahoo.com>
> Cc: pd-list <pd-list at iem.at>
> Sent: Thursday, November 17, 2011 4:34 PM
> Subject: Re: [PD] "get" method for Pd
> Would the device names and numbers from the Audio and MIDI settings be
> considered "gettable Pd attributes"?
They certainly are. However-- like canvas coords-- what's the best format
to get them in? If you separate them out into individual "attribute value"
messages they may be much easier to read and figure out, but a single
"attribute value(s)" message is easier to unpack/change/repack. Then
again, a single "attribute value(s)" message with lots of cryptic numeric
values is difficult to read-- just think about all the questions to the list about
what all the args for an iemgui mean, or donecanvasdialog, etc...
> If so, that would be awesome.
> On Wed, Nov 16, 2011 at 8:43 PM, Jonathan Wilkes <jancsika at yahoo.com>
>> I made a patch awhile back that added a "get" method to pd:
>> [; pd get version rcv-name( sends "version $major $minor
> $bugfix" to rcv-name
>> [; pd get dsp rcv-name( sends "dsp $status" to rcv-name
>> [; pd get * rcv-name( sends a sequence of all query-able "attribute
> values" to rcv-name
>> leaving off rcv-name will send the output to the Pd console
>> [; pd get( is synonymous with [; pd get *(
>> I remembered the patch when trying to generate crash logs for about.pd in
> the other thread--
>> if Pd has a "get" method then about.pd doesn't need to rely
> on externals (well, aside from
>> pddplink for the links).
>> Are there Pd attributes other than version and dsp status that would be
> nice to make "gettable"?
>> Pd-list at iem.at mailing list
>> UNSUBSCRIBE and account-management ->
> Mike Moser-Booth
> mmoserbooth at gmail.com
More information about the Pd-list