Jonathan Hallstrom

I've created a patch that allows me to move up in the pathname hierarchy (using regexp to strip off the pathname level of the folder the patcher lives in) so that I can generate new pathnames that access files in folders outside the one my patch lives in. Running it in Max works without a problem, but when I turn the patch into a collective and run it under Max Runtime in exactly the same configuration the patch returns nothing. I've attached a file with an example.

I've created a patch that allows me to move up in the pathname hierarchy (using regexp to strip off the pathname level of the folder the patcher lives in)  so that I can generate new pathnames that access files in folders outside the one my patch lives in.  Running it in Max works without a problem, but when I turn the patch into a collective and run it under Max Runtime in exactly the same configuration the patch returns nothing.  I've attached a file with an example. 

collective-wont-generate-file-path-names

The path message to thispatcher only works for max patches. That is, it stops working in a collective of standalone app, because there is no more the concept of a patcher. In a built application the message to max sendapppath can be used to find the location of the app. I believe in a collective there are no options, but you are only one step away from building an app; it's the same menu item.

In this thread a number of variations are discussed: 

https://cycling74.com/forums/a-workaround-path-to-standalone-from-within-standalone

In this thread a number of variations are discussed: https://cycling74.com/forums/a-workaround-path-to-standalone-from-within-standalone


Collective won't generate file path names