Save nested array.

Reply to Save nested array. on Sun, 16 Jun 2013 12:41:16 GMT

flappypineapple — Sun, 16 Jun 2013 12:41:16 GMT

i hope the title and my jargon/nonclementure is correct/appropriate

i'm having trouble with saving GUI settings in a nested array.
the array is in an object within the main patch.

basically the arrays are saving sequence data for recall. all works fine except saving.

when i open the nested patch containing the array and save it seperately, the new data is saved. if i only save the main patch, all updated array data is lost

how do i go about getting the arrays to save themselves
preferably without any user interaction, just closing the main window..

thanks.

ps i'm new here from Max. so i have limited knowledge of pd, and if any answers involve some sort of save path could you explain it briefly as its been a while since i've even messed with Max

Reply to Save nested array. on Sun, 16 Jun 2013 12:58:43 GMT

flappypineapple — Sun, 16 Jun 2013 12:58:43 GMT

lol it did just occur to me to put the arrays into a subpatch rather than than being nested .. then they save with the main patch...

but i still would like to know of a way to get a nested patch to save .

thanks.

Reply to Save nested array. on Tue, 18 Jun 2013 20:14:15 GMT

Maelstorm — Tue, 18 Jun 2013 20:14:15 GMT

By nested, do you mean abstraction? If so, it's not going to save in the abstraction, and that's not really behavior you'd want anyway. A better idea would be to put the array in the main patch and hand off the name of the array to the abstraction using an argument.

For example, say you have an array in the main patch called "myArray". Your abstraction would look like this:

[myAbstraction myArray]

Inside the abstraction, you could access it with dollar variables. [tabread $1] would read from myArray ($1 gets replaced by the first argument of the abstraction).

Reply to Save nested array. on Wed, 26 Jun 2013 05:15:25 GMT

flappypineapple — Wed, 26 Jun 2013 05:15:25 GMT

yes, nested is abstraction.
you're idea is exactly what i did

now i'm considering the final GUI and the best way to hide objects not utilised..

i've come across the graph on parent idea, making the subpatch an empty canvas. is this the best way to hide objects not necessary for the final GUI ?

i'll ask in another thread