Chris_DeCh

I have a patch that contains many nested sub-patchers. There are 2 colls used throughout so they can appear in many different sub-patchers within this patch. When I create a standalone application and then run the standalone application and look at the standalone console I see highlighted in red : 

The cols are named first and second. I'm building an application not a collective. Everything seems to work so there doesn't seem to be any issue with running the standalone . But are these errors or warnings normal ? Is there something about cols, their names and standalones that I may be missing. Do I need to somehow include them in the build script ?

I have a patch that contains many nested sub-patchers. There are 2 colls used throughout so they can appear in many different sub-patchers within this patch. When I create a standalone application and then run the standalone application and look at the standalone console I see highlighted in red : 
second: no such file in collective
first: no such file in collective

The cols are named first and second. I'm building an application not a collective. Everything seems to work so there doesn't seem to be any issue with  running the standalone . But are these errors or warnings normal ? Is there something about cols, their names and standalones that I may be missing.  Do I need to somehow include them in the build script ?

I have a patch that contains many nested sub-patchers. There are 2 colls used throughout so they can appear in many different sub-patchers w

stand-alone-error-or-warning-no-such-file-in-collective

In case someone has the same problem - I forgot that a name argument with a Coll object represents a text file. In a standalone simply add an empty text file to the resources folder for each Coll object in your patch.

In case someone has the same problem  - I forgot that a name argument with a  Coll object represents a text file. In a standalone simply add an empty text file to the resources folder for each Coll object in your patch.

An optional second argument will cause the coll object not to search for a file with the named symbol.

Try : {coll first 1}  and {coll second 1}
from coll help file :
An optional second argument will cause the coll object not to search for a file with the named symbol.


stand alone error or warning: no such file in collective