Brecht

I'm finishing up a patch for an installation right now and ran into a 

little quirk when building the standalone...

The error occurs when I load textures to the jit.gl.texture object 

and reads : jit.qt.movie : can't open resource 'filename.jpg'

I've tried including the files in the build, putting them in the same 

folder as the resulting appplication and the option 'utilize search 

path in preferences file' using the 'standalone' object.

None of which had any positive results... It all works fine when I 

load the textures in manually, so no errors or anything there...

Hi all!
I'm finishing up a patch for an installation right now and ran into a  
little quirk when building the standalone...
The error occurs when I load textures to the jit.gl.texture object  
and reads : jit.qt.movie : can't open resource 'filename.jpg'
I've tried including the files in the build, putting them in the same  
folder as the resulting appplication and the option 'utilize search  
path in preferences file' using the 'standalone' object.
None of which had any positive results... It all works fine when I  
load the textures in manually, so no errors or anything there...

another-standalone-question-cant-open-resource

put the jpg in the standalone package: ctl-click, select "show package contents" and navigate to Contents/MacOS and put the file there. That should probably work out for you!

put the jpg in the standalone package: ctl-click, select "show package contents" and navigate to Contents/MacOS and put the file there.  That should probably work out for you!


Make sure you don't include he file in the collective file (as saved 

in the collective builder/application builder window) *and* put 

inside the package's support folder. It will only find the version in 

the collective in this case. If you are experiencing these sorts of 

troubles, I would suggest only the latter (in the filesystem rather 

than in the collective file itself .mxf )

Make sure you don't include he file in the collective file (as saved  
in the collective builder/application builder window) *and* put  
inside the package's support folder. It will only find the version in  
the collective in this case. If you are experiencing these sorts of  
troubles, I would suggest only the latter (in the filesystem rather  
than in the collective file itself .mxf )

That's it! Works perfectly! Thanks a zillion, drinks on me!

Another standalone question : "can't open resource"