Folder error in standalone
Hi,
I'm getting an error only on the standalone version of my patcher:
Folder_Constr.: Macintosh HD:/Users/yogas/Desktop/ApplDest/
- error: js: FileList.js: Javascript ReferenceError: Folder is not
defined, line 745
The Code is:
742 function ceckIfExists(file_name, searchfolder_fullpath)
743 {
744 post("Folder_Constr.: "+searchfolder_fullpath+"n");
745 var found = false;
746 var f = new Folder(searchfolder_fullpath);
747 while (!f.end) .....
This code produces no error in MAXMSP.
Also I get those errors on startup pf my application:
- error: Macintosh
HD:/Users/yogas/Desktop/MakeMP3s.app/Contents/support/jsextensions/jsfolder:
loading old CFM externals disabled
- error: Macintosh
HD:/Users/yogas/Desktop/MakeMP3s.app/Contents/support/jsextensions/jsjitter:
loading old CFM externals disabled
- error: Macintosh
HD:/Users/yogas/Desktop/MakeMP3s.app/Contents/support/jsextensions/jstrigger:
loading old CFM externals disabled
Could there be a connection? Otherwise JS seems to run fine, as it
executes a lot of code before this folder thing.
Any Ideas?
Thanks and regards,
Stefan
According to the Javascript in MAX documentation, Folder is a 'js external object'. Its defined in an extension called jsfolder.mxe (in /Cycling '74/jsextensions on Windows)
You should maybe include that explicitly when you Build the application?
Hi Sean,
that was a good hint. It seems that by building the application an old
jsfolder file was put in the application package that wasn't even
present as a file on my computer. When I replaced that file (together
with the jsjitter and jstrigger, which also caused error messages) with
the actual files in the jsextensions folder you mentioned everything
went fine. No idea how this is possible. But can be reproduced. Maybe a
bug in the app building mechanism or chaos on my machine. Thanks.
Stefan
sean ahern wrote:
> According to the Javascript in MAX documentation, Folder is a 'js external object'. Its defined in an extension called jsfolder.mxe (in /Cycling '74/jsextensions on Windows)
>
> You should maybe include that explicitly when you Build the application?
>
I am more or less permanently cursed with this problem, & always have
to import the jsextensions by hand.
M
On May 9, 2007, at 19:25, Stefan wrote:
> Hi Sean,
> that was a good hint. It seems that by building the application an
> old jsfolder file was put in the application package that wasn't
> even present as a file on my computer. When I replaced that file
> (together with the jsjitter and jstrigger, which also caused error
> messages) with the actual files in the jsextensions folder you
> mentioned everything went fine. No idea how this is possible. But
> can be reproduced. Maybe a bug in the app building mechanism or
> chaos on my machine. Thanks.
>
> Stefan
>
> sean ahern wrote:
>> According to the Javascript in MAX documentation, Folder is a 'js
>> external object'. Its defined in an extension called
>> jsfolder.mxe (in /Cycling '74/jsextensions on Windows)
>>
>> You should maybe include that explicitly when you Build the
>> application?
On 11 mai 07, at 19:06, mattyo wrote:
> I am more or less permanently cursed with this problem, & always
> have to import the jsextensions by hand.
With MaxMSP 4.6.2 on a MacBook Pro, I can't reproduce the behavior.
Every time that I made an application jsfolder.mxo automatically
included in the myApp.app/Contents/support/jsextensions folder, as
long as the other files which were in my /Applications/MaxMSP 4.6/
Cycling '74/jsextentions folder. Which version of Max do you use, on
which plateform... ?
ej
Hi,
I'm sure now that my problem came from the updating process and as I
copied MaxMSP 4.6.1 from a G3 to an Intel MacBook Pro and updated to
4.6.2. there. The jsextensions that the app building script puts in the
app folder, are NOT on the MacBook Pro but are the ones which were on
the G3 (they keep even the finder labels). As I have some 3rd party
extension which makes it a bit complicated, I will wait for the next
update to make a new clean install.
Stefan
Emmanuel Jourdan wrote
> On 11 mai 07, at 19:06, mattyo wrote:
>
>> I am more or less permanently cursed with this problem, & always have
>> to import the jsextensions by hand.
>
> With MaxMSP 4.6.2 on a MacBook Pro, I can't reproduce the behavior.
> Every time that I made an application jsfolder.mxo automatically
> included in the myApp.app/Contents/support/jsextensions folder, as
> long as the other files which were in my /Applications/MaxMSP
> 4.6/Cycling '74/jsextentions folder. Which version of Max do you use,
> on which plateform... ?
>
> ej
>
>
>
On 11 mai 07, at 22:23, Stefan wrote:
> Hi,
> I'm sure now that my problem came from the updating process and as
> I copied MaxMSP 4.6.1 from a G3 to an Intel MacBook Pro and updated
> to 4.6.2. there. The jsextensions that the app building script puts
> in the app folder, are NOT on the MacBook Pro but are the ones
> which were on the G3 (they keep even the finder labels). As I have
> some 3rd party extension which makes it a bit complicated, I will
> wait for the next update to make a new clean install.
Backup everything, download the latest version, make a clean install.
ej
I'm running of a clean install, from basically the same system as
yours, but it may be picking them up from some bit or piece I
salvaged from my old machine -- I'l loork around, tidy up, &
reinstall...
Thanks,
M
On May 11, 2007, at 13:36, Emmanuel Jourdan wrote:
> On 11 mai 07, at 19:06, mattyo wrote:
>
>> I am more or less permanently cursed with this problem, & always
>> have to import the jsextensions by hand.
>
> With MaxMSP 4.6.2 on a MacBook Pro, I can't reproduce the behavior.
> Every time that I made an application jsfolder.mxo automatically
> included in the myApp.app/Contents/support/jsextensions folder, as
> long as the other files which were in my /Applications/MaxMSP 4.6/
> Cycling '74/jsextentions folder. Which version of Max do you use,
> on which plateform... ?
>
> ej
>
>