[PD] [PD-announce] Pd 0.43-2 released (windows startup bug fix)

[Jonathan Wilkes]

----- Original Message -----

> From: Charles Henry <czhenry at gmail.com>
> To: Jonathan Wilkes <jancsika at yahoo.com>
> Cc: "pd-list at iem.at" <pd-list at iem.at>; "pd-announce at iem.at" <pd-announce at iem.at>
> Sent: Monday, March 26, 2012 1:46 PM
> Subject: Re: [PD] [PD-announce] Pd 0.43-2 released (windows startup bug fix)
> 
> On 3/25/12, Jonathan Wilkes <jancsika at yahoo.com> wrote:
>>  ----- Original Message -----
>> 
>>>  From: Miller Puckette <msp at ucsd.edu>
>>>  To: pd-announce at iem.at
>>>  Cc:
>>>  Sent: Sunday, March 25, 2012 1:52 PM
>>>  Subject: [PD] [PD-announce] Pd 0.43-2 released (windows startup bug 
> fix)
>>> 
>>>  Hi all -
>>> 
>>>  Only Microsoft Windows users should care... but 0.43-2 is now finalized
>>>  (essentialy the same as the "test1" version), which fixes the 
> missing
>>>  TK
>>>  library problem on Microsoft Windows.
>>> 
>>>  I think things are reasonably stable now and I can turn to some
>>>  long-put-off
>>>  projects.  Foremost is a unification of message boxes with 
> "textfile"
>>>  functionality, and making a matching "message" type fr data 
> structures
>>>  (which will join "float", "symbol" and 
> "array".)
>> 
>>  I'm afraid whatever message type you come up with for data structures 
> will
>>  be
>>  severely limited unless you solve the problem of locality wrt data
>>  structures.
>>  Currently, one can choose either a) a modular approach with [struct 
> $0-name]
>>  which can be used inside abstractions, or b) state-savable [struct name]
>>  which
>>  is global and thus requires part of the user's brain power to remember 
> _not_
>>  to load more than one instance of the patch that contains the template.
> 
> An idea for workaround:  create your abstraction with one of each--a
> local $0-struct and a global-struct.  When loading the patch, write
> the data from global-struct into $0-struct, and if you intend to save
> the data, write the data back into global-struct before saving the
> patch.
> 
> or maybe you'd need to make two abstractions--one global with one
> instance for saved data, and many instances of your local version.
> This starts to sound bad...

The more I think about it, the more I think the data structure design itself 
is defective and is the culprit.  Reading/writing data structure data should 
be done through an object, not by sending read/write messages to the 
corresponding canvas.  Then you could specify the struct to the object 
whose function is to read/write scalar data, and it wouldn't have to save 
the struct name as part of the data.

-Jonathan

>