This is a simple question… I think. But can someone? Help me, I really don't know why people say that.

It's because some projects which use more than one “When green flag clicked” block might be a little laggy. Clicking the flag more than once might help with less lag on the project.

LionHeart70 wrote:

It's because some projects which use more than one “When green flag clicked” block might be a little laggy. Clicking the flag more than once might help with less lag on the project.

Thanks A lot!

GraspingVirus07 wrote:

This is a simple question… I think. But can someone? Help me, I really don't know why people say that.

If they say it they have a sloppily coded project. When coded neatly and efficiently, a project only needs the green flag clicked once.

When a project green flag is clicked, the green flag clicked blocks activate, but never at the same time. If the project has been coded poorly, one green flag clicked block activates before the other (which may have the resetting scripts under it). Parts of the project start up before the project has been fully reset.

People say double click the flag because sometimes their projects can be a little laggy and clicking the flag twice helps the project catch up I think…

scratchtwins-691 wrote:

People say double click the flag because sometimes their projects can be a little laggy and clicking the flag twice helps the project catch up I think…

Yeah, pretty much. Sometimes multiple clicks of the flag help the project's timing work better.

A lot of animations have that message in the instructions, and I think it's because of timing issues. But lag seems pretty likely too.

Basically, Scratch takes a while to load a sound (around 0.5 second delay) after it is played. You'll have to click the flag twice to remove the delay.

People say double click because they did not code their project correctly. Either they have multiple green flags setting off things that needed to be in a certain order or variables weren't initialized soon enough. If you only have one green flag and a start message, then you never have to double click a green flag.

And no, there is no “1/2 second delay” before a sound plays. The delay is 1/30th of a second at the most. HOWEVER, if in your sound file the first half second is silence, then it looks like a delay but it isn't. Edit the sound!

I find that I sometimes have issues with “double-clicking the flag”, but that's only on my note block project where, on the first time the project runs on most computers, the sound starts, delays the first block, and plays 2 - 3 notes at the same time, unfortunately. Double-clicking it seems to fix up the problem for whatever reason. I tried changing it to one green flag block (it used to be two) but nothing changed, so that's sometimes ONE of the reasons why you'd have to do that.

WolfCat67 wrote:

I find that I sometimes have issues with “double-clicking the flag”, but that's only on my note block project where, on the first time the project runs on most computers, the sound starts, delays the first block, and plays 2 - 3 notes at the same time, unfortunately. Double-clicking it seems to fix up the problem for whatever reason. I tried changing it to one green flag block (it used to be two) but nothing changed, so that's sometimes ONE of the reasons why you'd have to do that.

I would have to see the project to know why it doesn't work. Got a link?

footsocktoe wrote:

WolfCat67 wrote:

I find that I sometimes have issues with “double-clicking the flag”, but that's only on my note block project where, on the first time the project runs on most computers, the sound starts, delays the first block, and plays 2 - 3 notes at the same time, unfortunately. Double-clicking it seems to fix up the problem for whatever reason. I tried changing it to one green flag block (it used to be two) but nothing changed, so that's sometimes ONE of the reasons why you'd have to do that.

I would have to see the project to know why it doesn't work. Got a link?

It sometimes works properly, it sometimes doesn't; but here's the link. It'll take a LONG time to load though because I can't compact things properly and it has over 4000 scripts. There's also only one forever loop running at any given time while a song is playing (because none or more than one causes song lag):
https://scratch-mit-edu.ezproxyberklee.flo.org/projects/168423692/

Remember, the first thing that happens in the project is the green flag clicked broadcasts one message, and it starts a note block song immediately.

WolfCat67 wrote:

footsocktoe wrote:

WolfCat67 wrote:

I find that I sometimes have issues with “double-clicking the flag”, but that's only on my note block project where, on the first time the project runs on most computers, the sound starts, delays the first block, and plays 2 - 3 notes at the same time, unfortunately. Double-clicking it seems to fix up the problem for whatever reason. I tried changing it to one green flag block (it used to be two) but nothing changed, so that's sometimes ONE of the reasons why you'd have to do that.

I would have to see the project to know why it doesn't work. Got a link?

It sometimes works properly, it sometimes doesn't; but here's the link. It'll take a LONG time to load though because I can't compact things properly and it has over 4000 scripts. There's also only one forever loop running at any given time while a song is playing (because none or more than one causes song lag):
https://scratch-mit-edu.ezproxyberklee.flo.org/projects/168423692/

Remember, the first thing that happens in the project is the green flag clicked broadcasts one message, and it starts a note block song immediately.

That's a wonderful project! Having worked with note blocks myself, I know it's not always easy to get them synced and everything, but your project seems perfect to me. I experienced no delays or glitches.

As far as compacting goes, you can use lists and variables with note blocks, but I've always used them like you do, just plain from the can. It's probably worth experimenting with lists of notes if you are going to make another project like this. But I imagine you are completely burned out on note blocks after all the work this one must have taken.

Did you work from MIDI files of the songs? Are you a musician?

With projects with numerous resets and things that happen on startup, multi-clicking the green flag gets it all synced (usually) so the project works. I'm not so sure that the sloppy coding thing footsocktoe mentioned is always the case as you sometimes have to double or multi-click the flag on some of the best Scratchers' projects. So it's mostly for syncing scripts that run on startup.

ZZ9PluralZAlpha wrote:

I'm not so sure that the sloppy coding thing footsocktoe mentioned is always the case as you sometimes have to double or multi-click the flag on some of the best Scratchers' projects.

Many of the ‘best scratchers’ intentionally code their projects sloppily to make them look smarter/more complex and prevent other scratchers from understanding and using it. A pretty shady practice.

ZZ9PluralZAlpha wrote:

With projects with numerous resets and things that happen on startup, multi-clicking the green flag gets it all synced (usually) so the project works. I'm not so sure that the sloppy coding thing footsocktoe mentioned is always the case as you sometimes have to double or multi-click the flag on some of the best Scratchers' projects. So it's mostly for syncing scripts that run on startup.

That's the point. Write the code correctly in the first place so that the scripts sync properly. For example, have one green flag script that looks like this…

when green flag clicked
initialize global variables
broadcast [Initialize All Local Variables v] and wait
broadcast [Start v]

Each sprite has instead of a green flag the two hat blocks: “Initialize All Local Variables” and “Start”

Such a program will NEVER require a double click

Sometimes they say that because the project may be slightly buggy if the flag is only clicked once, like if it has lots or code or something.