What's Up with Tables?

clevername27

I had some Table questions, and from poking around the forum, there seem to be some other folks wondering around the same themes. Hopefully, this thread will serve as a reference point for all things Table.

Table Data

If I…

Engine.createAndRegisterTableData(0)

…that creates a Table object. I'm assuming that is abstract data that comprises a table—an array of points?

Previously (assuming I have this right), it was necessary to attach a Table Editor component to a Table Object, if you wanted to edit the points on the component. In that context, there are two sets of table data—the one in the component (used to draw the points) and a Table object, containing the data these points represent. By pointing the Table component to various Table objects, you can use one UI component to edit several sets of Table data. This also means that technically, you can simply store your table data as the points in just the Table component—and access to this data was just provided via a feature request by @d-healey.

Table Indexes

Does a table index refer to a Table controller, a Table object (an array of points, if that's accurate), or…something else?

What is the scope of a Table index? (In a ScriptNode Network, I think they're global to the Network?)

Answer: Table indexes are global to the Script Processor. (This explains why are they're global to a ScriptNode Network.)

Table Editor Components (ScriptTables)

If I simply create a table editor component, where/how is that data stored? (I haven't created a table object via Engine.createAndRegisterTableData(0))?

Exporting Data

Why is a Table Processor exported as a Base64 string, and Table data exported as an array?

Table Processors

I understand that a Table Processor allows you to use a table as the function for a modulator—but why is this object necessary, and what's inside?

Why is registerAtParent necessary, and how is it used?

Registering

Where does registerAtParent fit in?

Cheers and thanks!

Thanks!

d.healey

@clevername27 The table index if unique to the script processor. I posted a video to Patreon at the start of the month that makes use of sliderpack data objects, which is pretty much the same thing.

Just a moment...

(www.patreon.com)

Also in this video (ignore the global variable stuff, bad Dave, bad):
https://youtu.be/-0IEeFLTO5Q?si=O7atp0dvPLA0Bv-B

clevername27

@d-healey Thank you; that was a helpful piece of the puzzle. Oddly enough, I'm OK with slider packs. There seems to be an extra layer of complexity for Tables (which is good, because they're so flexible).

Brian

This post is deleted!