fabio

I have a coll named collData.txt in my patch (with "Save Data with Patcher" selected). If I write collData.txt in my patch folder, opening my patch the coll will bang out of the 3rd outlet despite the fact that there is no explicit read message... If I delete the collData.txt in the patch folder there is no bang. Does coll make a default lookup into the patch folder looking for "its" data? Any similar experience? If so, what about adding this odd "feature" to the help...?

Hi,
I have a coll named collData.txt in my patch (with "Save Data with Patcher" selected). If I write collData.txt in my patch folder, opening my patch the coll will bang out of the 3rd outlet despite the fact that there is no explicit read message... If I delete the collData.txt in the patch folder there is no bang. Does coll make a default lookup into the patch folder looking for "its" data? Any similar experience? If so, what about adding this odd "feature" to the help...?
Thanks
Fabio


coll-odd-bang-on-read

 message. It will open a file with the right name it's located in the search path. If you look in [p file_io] in the help file, you may find something interesting. You should also read the reference (the help files don't explain all features of an object).

coll doesn't need an explicit read message. It will open a file with the right name it's located in the search path. If you look in [p file_io] in the help file, you may find something interesting.  You should also read the reference (the help files don't explain all features of an object).

coll odd bang on read