@tomthebom
The Data Array is a tricky actor to work with as it stores values in an external text file. It is extensible, which means you determine the number of data values in the matrix and the variables of each of the data values are stored in corresponding 'lines' in an external text file. If I specify 10 data values (these are referred to as 'items' in the data array actor), 10 delimited values are stored across one line in the text file and the line number is then used to call up a corresponding set of data values or 'items'. The text file can store a growing number of lines (sets of item values) and the data array actor can read and write the item values within these 'lines' to the text file. The way to edit the 'items' in the text file is to determine the values of a set of items and then record them using the actor inputs: recall, erase, add, insert, replace, delete. None of the functionality to write, store, retrieve and edit the data array sets (stored in 'lines') is intuitive and the layout of the actor adds additional hurdles in determining what is being written to the text file and in what line order - hence it is both a powerful and frustrating actor to work with. It is very easy to inadvertently overwrite a specific line of values because the 'index' input is set to the wrong line number. In addition input values that can be written to the text file do not visually align with current values being read - therefore I recommend the construction of a user actor so that some sense can be made of data writing to the text file and data being read from the same text file and exactly where lines are being inserted or replaced. Initially, I worked with the data sets as lines in the text file itself as it was easier to access, copy and paste lines of values or tweak values in the text file, rather than wrangle the read and write functionality of the data array actor itself. A good starting point is the Isadora manual.