This content has been marked as final. Show 6 replies
I believe this was introduced in version 10. The default location to save files was moved to the Windows User Profile directory. This is why you are seeing the files appearing in the My Documents folder.
To further complicate things, you might get different results when running in authoring vs. running from projector. This is because in authoring the "projector" is the Director app and thus, located at (typically) C:\Program Files\Macromedia\Director MX 2004\
Windows XP doesn't always like for files to be written there and thus saves to My Documents.
Further more, with the coming of Windows Vista, this is actually a desired result because of new security restrictions involved with saving out files.
Run this little test from both authoring and a projector.
Place a text member on stage (say sprite(5)).
In the frame add...
sprite(5).member.text = the moviePath
Sorry, I don´t know what you mean, I tried to put that in the script, but it doesn´t work. I execute the file in this form:
But as you say the file is generated in the other place...
My point was to build a little test file and see the difference between the moviePath variable in projector vs. authoring.
Have you tried the open() function from a projector or just authoring environment?
I don't know what you mean between proyector or authoring environment?
When you are using Director to build your application, you are in the authoring environment.
When you Publish a .exe file that is a Projector. When you run the Projector you are in the Projector environment.
When dealing with paths, these two environments will act differently and return completely different information.
You could try using Buddy API's baShell() command and set the working
directory to where you want. I don't know whether this will achieve what
you need, though a quick test might confirm.