Carl Emil Carlsen

strange-standalone-error-no-such-object

i'm a bit mystified why this happens, I'm guessing that is has something to do with the object mapping system (you can't have a file called "*~.mxo" becuase * is not a legal filename character, so it maps to times~.mxo). 

You can simply add the times~.mxo from your externals folder and put it in the application package Contents/ folder (ctl-click on the app icon and select "Show package contents).

i'm a bit mystified why this happens, I'm guessing that is has something to do with the object mapping system (you can't have a file called "*~.mxo" becuase * is not a legal filename character, so it maps to times~.mxo). 
You can simply add the times~.mxo from your externals folder and put it in the application package Contents/ folder (ctl-click on the app icon and select "Show package contents).


I did just that and now the standalone opens without error 

messages ... still it doesn't work though, no video output. Debugging 

blindfolded is the worst pestilence. I'll return as soon as I can 

> You can simply add the times~.mxo[...]
I did just that and now the standalone opens without error  
messages ... still it doesn't work though, no video output. Debugging  
blindfolded is the worst pestilence. I'll return as soon as I can  
come up with a clever question.

copying everything from the c74 folder works, but if you want to streamline your standalone a bit on OSX, you can just note the missing object errors in the Status window, then build an Automator script that gathers only the things you need into a folder, then put the contents of that folder into the app package.

sure, thats the nice solution... i was pretty straightforward to the end-user

But... how does your script do when your application is loading and scripting

external abstractions not necessarily compiled with the built?

Do you have an automated beta-tester lauching all the functions of your app? 8)

Now, dear Peter, would you by chance share this wonderful bit of script that

make this nice job you describe with the community? ;)

> copying everything from the c74 folder works, but if you want to streamline

> your standalone a bit on OSX, you can just note the missing object errors in

> the Status window, then build an Automator script that gathers only the

> things you need into a folder, then put the contents of that folder into the

sure, thats the nice solution... i was pretty straightforward to the end-user
result who want things to run.
But... how does your script do when your application is loading and scripting
external abstractions not necessarily compiled with the built?
Do you have an automated beta-tester lauching all the functions of your app? 8)
Now, dear Peter, would you by chance share this wonderful bit of script that
make this nice job you describe with the community? ;)
best
vincent

>
> copying everything from the c74 folder works, but if you want to streamline
> your standalone a bit on OSX, you can just note the missing object errors in
> the Status window, then build an Automator script that gathers only the
> things you need into a folder, then put the contents of that folder into the
> app package.
>
>


"But... how does your script do when your application is loading and scripting external abstractions not necessarily compiled with the built?"

I just have to go through my standalone and test it and find all the "not found" errors, and make note of what patches and externals need to be part of the Automator script. It's a mildly arduous process, but worth it in the end. And since I made the patch, I have a good idea when things are scripted, so I know where to look. It's made a bit easier by copying the contents of the status window, putting it into TextWrangler, and searching for all the relevant "error: can't find" etc.

I could share the script, but of course it points to all the files on my machine, and wouldn't be much use to anyone else.

However, in Automator, the functions used are:

+ "New Folder" (I tell it to create a folder on the desktop)

+ "Get Specified Finder Items" (where I can drag drop all the files I need to get). It is worth noting that I don't pass any data from the first step to this one - see attached picture.

+ "Copy Finder Items" (to the new folder)

So, no it's not all automagic to begin with, but it does make the process a bit easier and the resulting standalone a bit smaller.

I just have to go through my standalone and test it and find all the "not found" errors, and make note of what patches and externals need to be part of the Automator script.  It's a mildly arduous process, but worth it in the end. And since I made the patch, I have a good idea when things are scripted, so I know where to look.   It's made a bit easier by copying the contents of the status window, putting it into TextWrangler, and searching for all the relevant "error: can't find" etc.
I could share the script, but of course it points to all the files on my machine, and wouldn't be much use to anyone else.
However, in Automator, the functions used are:
+ "New Folder" (I tell it to create a folder on the desktop)
+ "Get Specified Finder Items" (where I can drag drop all the files I need to get). It is worth noting that I don't pass any data from the first step to this one - see attached picture.
+ "Copy Finder Items" (to the new folder)

STRANGE Standalone error: *~: No such object