Discuss Scratch
- Discussion Forums
- » Bugs and Glitches
- » uhm... can't stop my project?
- iSCRATCH456
-
21 posts
uhm... can't stop my project?
My browser / operating system: Windows NT 10.0, Chrome 137.0.0.0, No Flash version detected
uh… I went into my project, clicked the green flag, and how when I try to press the stop sign, nothing happens. I don't have any forever loops going, if that's relevant. It just wont stop for some reason.
uh… I went into my project, clicked the green flag, and how when I try to press the stop sign, nothing happens. I don't have any forever loops going, if that's relevant. It just wont stop for some reason.
- ispretty
-
500+ posts
uhm... can't stop my project?
not really sure why, but if you have this block: My browser / operating system: Windows NT 10.0, Chrome 137.0.0.0, No Flash version detected
uh… I went into my project, clicked the green flag, and how when I try to press the stop sign, nothing happens. I don't have any forever loops going, if that's relevant. It just wont stop for some reason.
when [loudness v] > (10)the project cannot be stopped even if the loudness or timer value is less than the number in the input
Last edited by ispretty (May 30, 2025 01:47:17)
- michaeljackson1365
-
1000+ posts
uhm... can't stop my project?
That block only fires up the project if you make a sound louder than that.not really sure why, but if you have this block: My browser / operating system: Windows NT 10.0, Chrome 137.0.0.0, No Flash version detected
uh… I went into my project, clicked the green flag, and how when I try to press the stop sign, nothing happens. I don't have any forever loops going, if that's relevant. It just wont stop for some reason.when [loudness v] > (10)the project cannot be stopped even if the loudness or timer value is less than the number in the input
when [timer v] > (10)
- ispretty
-
500+ posts
uhm... can't stop my project?
yes but the project still continues to run even if the block isn't firingThat block only fires up the project if you make a sound louder than that.not really sure why, but if you have this block: My browser / operating system: Windows NT 10.0, Chrome 137.0.0.0, No Flash version detected
uh… I went into my project, clicked the green flag, and how when I try to press the stop sign, nothing happens. I don't have any forever loops going, if that's relevant. It just wont stop for some reason.when [loudness v] > (10)the project cannot be stopped even if the loudness or timer value is less than the number in the inputwhen [timer v] > (10)
- nembence
-
100+ posts
uhm... can't stop my project?
Are scripts still running after clicking the stop sign, or is just the green flag highighted?
If there is a
The green flag is highlighted because how these hat blocks work internally:
If there is a
when [timer v] > (10)or a
when ( v) pressed in order // or any other green hat blockin the project, then the green flag stays highlighted after clicking the stop sign. I think this is normal, and the stop sign should still stop all scripts (but the hat blocks might re-activate them later).
The green flag is highlighted because how these hat blocks work internally:
<{
when [timer v] \> (10)
do something::custom
}[\=]<{
when @greenFlag or @stopSign clicked::#008 hat
forever
wait until <(timer)\>(10)>
do something::custom
wait until <not <(timer)\>(10)>>
end
}::grey ring>::#fff ring>
[/scratchblocks][Why do I need two {/scratchblocks} tags]
- ispretty
-
500+ posts
uhm... can't stop my project?
I didn't know that the extension blocks also did that. Are scripts still running after clicking the stop sign, or is just the green flag highighted?
If there is awhen [timer v] > (10)or awhen ( v) pressed in order // or any other green hat blockin the project, then the green flag stays highlighted after clicking the stop sign. I think this is normal, and the stop sign should still stop all scripts (but the hat blocks might re-activate them later).
The green flag is highlighted because how these hat blocks work internally:<{
when [timer v] \> (10)
do something::custom
}[\=]<{
when @greenFlag or @stopSign clicked::#008 hat
forever
wait until <(timer)\>(10)>
do something::custom
wait until <not <(timer)\>(10)>>
end
}::grey ring>::#fff ring>
[/scratchblocks][Why do I need two {/scratchblocks} tags]
It's not really normal (or at least necessary) for this to happen, as the workaround argument can also be made for the yellow key press block
<{and yet it doesn't keep the project running
when [ v] key pressed
do something::custom
}[\=]<{
when @greenFlag licked::#008 hat
forever
wait until <key [... v] pressed?>
do something::custom
wait until <not <key [... v] pressed?>>
end
}::grey ring>::#fff ring>
- iSCRATCH456
-
21 posts
uhm... can't stop my project?
not really sure why, but if you have this block: My browser / operating system: Windows NT 10.0, Chrome 137.0.0.0, No Flash version detected
uh… I went into my project, clicked the green flag, and how when I try to press the stop sign, nothing happens. I don't have any forever loops going, if that's relevant. It just wont stop for some reason.when [loudness v] > (10)the project cannot be stopped even if the loudness or timer value is less than the number in the input
Are scripts still running after clicking the stop sign, or is just the green flag highighted?
If there is awhen [timer v] > (10)or awhen ( v) pressed in order // or any other green hat blockin the project, then the green flag stays highlighted after clicking the stop sign. I think this is normal, and the stop sign should still stop all scripts (but the hat blocks might re-activate them later).
The green flag is highlighted because how these hat blocks work internally:<{
when [timer v] \> (10)
do something::custom
}[\=]<{
when @greenFlag or @stopSign clicked::#008 hat
forever
wait until <(timer)\>(10)>
do something::custom
wait until <not <(timer)\>(10)>>
end
}::grey ring>::#fff ring>
[/scratchblocks][Why do I need two {/scratchblocks} tags]
Thank you to everyone for your help, I fixed it!
- Discussion Forums
- » Bugs and Glitches
-
» uhm... can't stop my project?