> The "path" of a patcher in a standalone of collective is not a
> really meaningful - the path of the *application* is what you're
No it isn't. If I'm loading a patcher from disk (NOT from within the collective) as a user-selectable component of my app, I might conceivably want to know where that was loaded from so I can look for additional components there. Sure, there are other ways to get this info, but that's no reason why path->thispatcher shouldn't be usable.
Reading this thread again, I don't get why or how does 'path' -> thispatcher -> absolutepath work in collective. What does thispatcher output when in a collective ? I attached various [print], message boxes or [printit] to see what is going out but it doesn't help. What is the magic ?
Hi there, I'm trying to solve the same problem here... I'm building a collective, and I need the program to be able to find out where it is saved in order to save some sound files and retrieve them again.
I prefer using collective because it is cross platform, so I can just save one version and use it on windows as well as mac.