relevante

I'm working on a patch that integrates a number of other patches together using a bpatcher that contains numerous patcher objects that reference my external patches. In some of these individual patches I'm accessing images to load as textures, or jxf files that I'm reading and writing to cache things. Running individually this works fine, but once I put them in the bpatcher I can't find any combination of moving files or the filepath object that seems to do anything. I eventually need to compile this as an app, but it really should work in patcher mode as well.

I'm working on a patch that integrates a number of other patches together using a bpatcher that contains numerous patcher objects that reference my external patches.  In some of these individual patches I'm accessing images to load as textures, or jxf files that I'm reading and writing to cache things.  Running individually this works fine, but once I put them in the bpatcher I can't find any combination of moving files or the filepath object that seems to do anything.  I eventually need to compile this as an app, but it really should work in patcher mode as well.

bpatcher-filepath-fail

attached is one way of many to do this (what i think you are trying to do). you put a thispatcher in your main patch, construct a path to a folder of media relative to your main patch location, and send this path to you bpatchers.

each bpatcher has a argument that sets the name of the asset they are supposed to load.

this solution will port to standalones, but you have replace thispatcher with the max message "sendapppath".

with some clever patching, and use of the "getruntime" and "getsystem" messages, you can come up with a solution that supports normal patching, mac standalones and windows standalones.

attached is one way of many to do this (what i think you are trying to do).  you put a thispatcher in your main patch, construct a path to a folder of media relative to your main patch location, and send this path to you bpatchers.

Thanks a lot for the reply and example. Unfortunately though I seem to be having some weirder issue. It's not just an issue of getting the absolute path to the file. I've resigned myself to just hard-coding that. Yet even with a fully qualified absolute path, things aren't working. However looking at your example has led me to discover something else interesting.

JS can find the file while I'm running in the full bpatcher arrangement (using new File()) at the absolute path. But when I pass the path to the file attribute of my jit.gl.texture that textures my jit.gl.gridshape object in javascript it doesn't work. It doesn't throw any errors, but it doesn't texture my object. If I'm not in the bpatcher it works flawlessly.

This is odd in itself, but even more odd is that if I throw some junk into the path or filename so that it's pointing at a file that doesn't exist it fails (obviously), but now it throws a jit.qt.movie can't find file error. So when the path is correct that it is actually finding the file, as evidenced by the fact that it throws an error only when the path is incorrect, but it just doesn't actually use the file to texture the object. Again it all works fine with the exact same patch with the exact same absolute path to the exact same image files when it's not included in a bpatcher.

Thanks a lot for the reply and example.  Unfortunately though I seem to be having some weirder issue.  It's not just an issue of getting the absolute path to the file.  I've resigned myself to just hard-coding that.  Yet even with a fully qualified absolute path, things aren't working.  However looking at your example has led me to discover something else interesting.

JS can find the file while I'm running in the full bpatcher arrangement (using new File()) at the absolute path.  But when I pass the path to the file attribute of my jit.gl.texture that textures my jit.gl.gridshape object in javascript it doesn't work.  It doesn't throw any errors, but it doesn't texture my object.  If I'm not in the bpatcher it works flawlessly.

This is odd in itself, but even more odd is that if I throw some junk into the path or filename so that it's pointing at a file that doesn't exist it fails (obviously), but now it throws a jit.qt.movie can't find file error.  So when the path is correct that it is actually finding the file, as evidenced by the fact that it throws an error only when the path is incorrect, but it just doesn't actually use the file to texture the object.  Again it all works fine with the exact same patch with the exact same absolute path to the exact same image files when it's not included in a bpatcher.

bpatcher filepath FAIL