Hi all,

I've been using the SSSAD preset system with some of my abstractions for the $0-receives/sends and it works great. However, some of my abstractions use table data. I can export and import the table data to a textfile using [openpanel] and [savepanel] however, with this method, I then end up with two textfiles for preset data, - one that the SSSAD abstraction creates and another that I create to save my abstracted table data in. Is there a way to combine these two textfiles into one so the SSSAD system reads the $0-receives/sends as well as the abstracted table data from one textfile which contains all the preset data?

All the best

Casper

@casper Hello Casper.....
I have never used it (SSSAD) but I just had a quick look at the help file. I would think that you could play out your table data with [tabread] through [list prepend] and give the resulting list a "Key Name"............
Come back if you cannot work out how to get the data back........
maybe.pd
David.

Hi @whale-av thanks for this, this has really helped. I've tried to get it interacting with the SSAD system. So I've produced an abstraction called presetable to sit inside a 'working project' called presettablescreen.

The contents of the presetable abstraction is below

So I can't figure out how to get the {sssad $1/table] object to output the table list (from the textfile (tablesettings.txt) and rewrite it into the [tabwrite $0-table1] object.

The contents of the textfile is below:

My presettable workspace project is below to using the SSSAD subpatch to create the textfile etc.

Any ideas would be great. I've included the patches in this post.

presettable.pd
presettablescreen.pd
tablesettings.txt

cheers

Casper

@casper .....................
If you are not using extended you will have to build an alternative to [drip] using [list split] and [list append]........
maybe2.pd
David.

@whale-av you are a jedi ! Thank you so much this. This system now works with the SSSAD system to preset table values

@casper Glad to help! I will have to look into it more. It is a nice idea to have a system sitting in the background taking/saving and sending back whatever you throw at it.
There is a more complex setup for "extended_view_toolkit" called "kollabs", but SSSAD seems much easier to adapt to your own patches.......
David.