jnetman1 wrote:
How do I prevent projects from starting automatically when presented online using ScratchApplet? I'd prefer that they wait until the flag is clicked.
maybe a:
[blocks] <wait( # here )secs> [/blocks] but i'm not to sure what ur talking about?
Last edited by golfer3 (2009-03-19 19:55:08)
Offline
I mean when a page that uses ScratchApplet first loads, the applet starts the attached project automatically. For example, if I open the Bug on a Plate sample program in Scratch, the first thing I see is the instructions until I click on the flag. If I place it in a web page with ScratchApplet, it doesn't show the instructions, instead acting like I clicked the flag already. If I click Stop, then I see the instructions as expected. Same thing with the PianoMachine sample project. In the project, there is an explicit "when flag clicked" subroutine. However, in a web browser, it immediately starts bouncing the balls as if the flag was clicked. Same experience with our own projects. I want these to behave the same way in a web browser as they do in the Scratch application.
Offline
jnetman1 wrote:
I mean when a page that uses ScratchApplet first loads, the applet starts the attached project automatically. For example, if I open the Bug on a Plate sample program in Scratch, the first thing I see is the instructions until I click on the flag. If I place it in a web page with ScratchApplet, it doesn't show the instructions, instead acting like I clicked the flag already. If I click Stop, then I see the instructions as expected. Same thing with the PianoMachine sample project. In the project, there is an explicit "when flag clicked" subroutine. However, in a web browser, it immediately starts bouncing the balls as if the flag was clicked. Same experience with our own projects. I want these to behave the same way in a web browser as they do in the Scratch application.
you can program every thing with a [blocks]
<when[ ]key pressed> instead of a <when green flag clicked>[/blocks]
Offline