First Quote mark is in the wrong place.
Thanks for your quick response. But I'm afraid I mistyped the second one.
movie.go(1,"@Chapter1/W1_1sim <mailto:1@Chapter_1/W1_1sim> ")
but this one didn't.
I apologize for the confusion. As a 79 year old I probably shouldn't be doing this anymore.
I was hopeful that it was just a misplaced quote mark.
I tried your code on my XP SP3 system and it works fine. I created the folders, the Director files, and used:
on mouseDown me
I have no idea why the code does not work for you. Do you get an error message?
Perhaps there is a typo that you are not seeing. You should have someone else take a look at it. In my past I have wasted countless hours searching for a bug that I was blind to. I ask someone else to read the code and instantly they can see the typo that I was blind to.
To demonstrate how wierd this problem is I have attached copies of the screen where in the first one Lingo is asking where the file is that is right below it and then in the second frame that follows the first is the inability to find it.
I will create new alternative files with more comact names and see if that is the problem. But it takes a while to do that.
Thanks again for your support.
If I remember correctly some objects don't like certain characters in their names.
You might want to try removing the hyphens.
Problem Solved ... Cause remains a mystery
I am happy to report that I got the Director program to work like it should. I have two major folders for this project: one where the projector is created that includes script files for it all photos and video ... some of which may not appear in the final version and when I get the projector to work I copy it into the final folder along with accompanying QT movies. So I finally gave up on the previous projector in the final folder and recopied a copy (with a different name) into the final folder, then used exactly the same _movie.go... command and everything worked! So I moved the troublesome projector into the trash but never really understood what the problem was.
At any rate, I appreciate the effort you put into this and your helpful suggestions.
Thanks Jim. I was worried about that as well. But then I replaced it with a different projector using the same name protocol and it worked. So I don't know what was going on but the good news is that the problem is solved.
Thanks for your comment.