Hi, I'm having a strange problem with the Data Array actor reading files.
The file path is /Users/craigw/Documents/IsadoraFiles/Games/Headsup/Headsup v2/Lookup Files/headsup1.txt
If I change one thing in the Data Array path the the forward slashes / turn into underscore _ and it no longer reads. Even if I manually type them back in it turns back into underscore on it's own.
The Data Array is such a great node for extending the possibilities of working with Isadora—bit of a learning curve—but great!
There are two flavours of the Data Array and your two screen shots show one of each. The first screen shot is the older (and now renamed) 'Classic Data Array' that allows associated .txt files in long directory paths e.g. /Users/jc199482/Documents/Data01/Data02/Data03/data.txt.
You can distinguish the two variants by looking for the 'local copy' parameter—the Classic Data Array doesn't have it.
Your second screen grab demonstrates the newer Data Array (with the 'local copy' parameter). I experience the same behaviour, but I wonder if it is not expected behaviour as the newer Data Array likes to have its data source close by—in the same location as the .izz file.
I did some experiments with path input and found that the resulting .txt file always appeared in the same location as the .izz file—no matter what path I fed it. so the file path:
resulted in a text file named: "_Users_Rupture01_Documents_whatsUP_whatsUP2_whatsUP3_whatsUP1.txt" located in the same folder as the Isadora file with the newer Data Array that generated it. It appears to purposely force the data text file to stick close to the host Isadora file.
The Classic Data Array only does numbers, but it works everytime.
Hi, Doing a simple build with the data array in v3.07 seems to work, but v3.08 doesn't.
<p>Hi, Doing a simple build with the data array in v3.07 seems to work, but v3.08 doesn't.</p>
Can you share these builds so that I can confirm the problem and have it corrected?
Yes, it appears some url cleaning made its way into the Data Array actor. I have entered this bug and expect it will be fixed for an upcoming release.
In the meantime, if you place the data file in the same folder as the Isadora file, you can just use the data file name eg: "data.txt" and everything works as expected.
Hopefully that is an option for you.
Thanks for verifying that it is a bug.
Thank You, I try your idea.
Works perfectly! Great work around.