that's by design. after all, you'd usually use [table] or [array define] if you don't really need the graphical representation. otherwise, you'd use the graphical array from the menu.
 
> Basically: is [array] simply a nicer wrapper for an "array" (menu: put -> array) or is the underlying data structure different?
 
[array define] and [table] both contain a graphical array (which itself is just a graph - a subpatch with GOP enabled - containing the actual data structure).
there are some subtle differences, though. for example, you can't save the content of a [table] in your patch, but you can with [array define -k].
[array] is not editable, [table] is - but changes are not saved.
 
Christof
Gesendet: Donnerstag, 23. November 2017 um 18:34 Uhr
Von: Alex <x37v.alex@gmail.com>
An: "PD List send" <pd-list@iem.at>
Betreff: [PD] array/[table] vs [array] curiosity
Some friends and I were preparing to teach a workshop a few weeks ago and while looking through the [table] help file we saw:
 
[array]: (newer and better replacement for "table")
 
which inspired some questions..
 
Basically: is [array] simply a nicer wrapper for an "array" (menu: put -> array) or is the underlying data structure different?
 
I see if you create an object [array define] you get an object that opens a window on click, subpatch style, into a visualization of that array, but inside that window you can't edit properties (though maybe that is a bug because when I go to properties I get a message: "array: no method for 'done-popup'" in the main window).
 
Thanks,
Alex
_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list