Algodoo

Why? It's a subject that needs a lot of talking so that kids will get the message. We cannot save everyone because not everyone will listen and take this advice. If even just a few kids grow up without smoking cigarettes or vaping, then all this talk will be worth it.

No, because it's too much trouble to make the sound work properly. Maybe someday Algodoo will get an update which includes the ability to produce sound but I wouldn't hold my breath. The cost to add new features to an old software product is usually too high to be practical, especially for a product that is FREE to the public.

That's who he looks like! I saw the real Penny Wise in a storm drain in front of my house the other day. He kept begging me to come over to talk to him, but I was too busy at the time. Maybe later.

Oh, Okay. Now it makes sense!

I changed the word in your scene title for you. I hope you don't mind.

Your Tetris project? Sorry, but I looked at all the scenes you posted on Algobox and I don't see any titled "Tetris project".

rjoseph -- You make no sense. Can you be more specific about what you are asking?

Okay, great!


Oops, hold on there. I have one more correction for ya. You stated "Naming the variable with a _ at the start makes them easier to spot." Well, my friend, that's not all the underscore is for. It is required for all local (also called "custom") variables. Without the underscore character, the variable will not be saved with the scene which means that it will not work whenever anyone downloads your scene and tries to use it! The underscore character is NOT needed for global ("scene.my...") variables.

Rick is ubiquitous!

Hmmmm... I don't remember that one. Can you give me the actual link to it? Copy the url then paste it into a comment.

Not that I know of. I've tried extending the zoom limits for one of my older scenes but without success. I'm sure that it's limited for a good reason.

No particular reason. It just happens to be the way I made the scene. It was probably due to the fact that I'm right-handed, and so it's easier for me to grab the bleach on the right-hand side of the scene. Why do you ask such strange questions?

YW!

Oh, wait... I just thought of one more thing (that stuff happens to us old people). You also do not need the underscore character for temporary variables. Temporary variables can be used within a calculation or within a function. For example:

{
tempVar = math.sin(sim.time);
tempVar > 0.5 ? {do this}:{else, do this}
}

After that code is no longer executing, tempVar will no longer exist.

Don't worry, donnie. I don't worry about people copying things without permission because, as I stated in my own scene about giving credit, it's impossible to know who the original owner is. Stuff gets copied and reused practically every day here on Algobox, and I'm not going to spend many hours of my time trying to determine who actually created a particular ragdoll or a particular blue marble. I have better things to do with my time!

Oh, now I know what you are referring to! I thought you were saying that you were playing Mario Kart and you saw MY NAME in that game! LOL

Anyhow, see my earlier comment about why I made this scene...

Africa will be up in the sky with clouds floating by?

Blocking your camera won't help, s_noonan. I wrote a script that activates the pixels in your monitor to become light sensors instead of light emitters. I can see you blushing as I compose this comment. (please put your pants back on!)

How? I made one green, one yellow, one blue, one orange, and one red. Sorry rjoseph, but that was a dumb question.

Secure pipes? What the heck is a secure pipe?

Okay, now I know why the confusion. You are located in the U.K. We don't have something called "secure pipes" here in the U.S. as far as I know. I did a search on Google and the only thing I found called secure pipes is something to do with computer programming.

Nice job, Little!

WOW! Very impressive coding! I'm looking forward to the completed game.

This is cool! It reminds me of the time I worked for a company repairing the old school (electro-mechanical) pinball machines.

Red was tossed into burning hot lava at the bottom of a volcano.

The keys are very difficult to read because you have white numbers on very light-colored keys. You can fix that by: Right-click on a key, then hover your cursor over "text". When the text configuration panel shows, simply click on the color black. Do that for all keys, then save your edited scene and upload it to Algobox. Problem solved!

Oh, one more thing: There's no reason to have clouds floating by for a calculator! You can disable the clouds this way: Right click on the background, then uncheck the "draw clouds" checkbox.

The time-delay fuse turns red but the grenade does not explode! The reason is because the time-delay fuse is a polygon, and polygons do not have protractors. It will work if you use something else besides a protractor for the chain reaction.

Suggestion: Test your scenes after uploading them. I learned that lesson a long time ago!

Why?

Does it work when you download the scene from Algobox?

Wow! I felt like I was going inside of Rick's mouth!

Very good job! Well-made puzzle, and it works perfectly!

Your calculator buttons are much easier to read now. Good job!

Oh, here is one more suggestion that I should have mentioned before but I forgot to. The display begins with "undefined" which is not normal for a calculator. You can fix that by initializing the variable scene.my.display with a value of zero. You can do that by placing scene.my.display = 0 in onSpawn. It will look like this: onSpawn = (e)=> {scene.my.display = 0 }