Scratch

Yeah Hobbs is right. I've got the same problem.

Hobbs1100 wrote:

bump

If you're looking for an explanation of why things work differently on the web...I'll take a whack at it.  On the web, your project is running in a piece of code written in Java that interprets the Scratch project and runs it.  When you run it downloaded, you are running in the Scratch integrated design environment (IDE) which is written in Squeak.  So, because of differences in the two players (Java and Scratch), you can get differences in the timing of events as the project runs.  So if you have a bunch of things set up to run on Green Flag you might get one sequence of events in one player and another in the other player.  This can cause problems if one of the events depends on the other event running first (such as variable initialization).  You can often cure online problems by thinking hard about what really needs to happen in what order and making sure that it really happens in that order by using short WAITs or broadcast messages.

Of course, there are other differences between the players that you just have to work around.  Such as the maximum sprite size (no bigger than the screen, online) and the fact that "When Clicked" works differently (I usually use Mouse Down and Touching Mouse instead). 

I don't know if there are going to be significant changes to the Java Player with the 1.3 release.  We can hope that some of these issues go away...but I'm pretty sure that there will always be differences as long as there are two separate players. 

In the programming industry, it's pretty common to maintain a program on multiple platforms with the same set of source code (which is pretty much what's going on here with the Scratch and Java platforms).  You are actually getting some good experience with the sort of problems that can occur when you try and do that.   So...if you're looking for a silver lining - there it is!  That having been said, I do hope some of the issues are cleared up.