cudell

I have a max patch that uses js newdefault() to generate objects on the fly.

In the full version of Max, when I hit save, these generated objects are saved and appear the next time I open the file.

However: When I try and generate these object in runtime - I cannot save these for the next time I open the patch.

Question: Is there some way to save the state of all objects and connections in a patch in runtime so that objects generated using scripting stay preserved for the next time the patch opens?

I've tried sending a "write" message to [thispatcher]

Hi Community;
I have a max patch that uses js newdefault() to generate objects on the fly.
In the full version of Max, when I hit save, these generated objects are saved and appear the next time I open the file. 

I've tried sending a "write" message to [thispatcher]
Much thanks.
Chet


saving-script-generated-newdefault-objects-and-patch-cords-in-runtime

I'd very much like to save the most recent state of my user-generated scripted objects and patch cords from runtime

** Poking this thread ** Any ideas??
I'd very much like to save the most recent state of my user-generated scripted objects and patch cords from runtime

While I'm not too hopeful that this functionality exists, I too am very keen to know if there's a way to achieve this.

My patch similarly allows users to dynamically create and connect a modular system of bpatchers, via in built scripting, all from presentation mode (although no js is used to accomplish this).

I'd love a way for users who don't own max to be able to save their creations.

Is there a hack method to achieve this? Maybe it requires saving all order of creation and connections made into a coll or something (which can be saved to disk as text file) and then when the patch is reloaded (from runtime), the coll is read through and the patch is rebuilt again in the order the user created it???

Has anyone tried this before with success?

Saving script-generated (newdefault) objects and patch cords in Runtime