Algodoo

Nice effect on the thrusters! It looks great!

I let the ball spin up too fast before releasing it. Now the Moon has a new crater on its surface.

I moved the script from update to postStep so that it runs only when Algodoo is running, and it seems to still work properly. If you would move the script to update in all 64 boxes, then people will be able to select boxes and make changes without the scene constantly running.

This is interesting but I don't understand how it can be used in other programs like Paint, etc. Please explain.

Thanks!

Could you please explain how your function scene.my.display works? I cannot figure it out by myself.

Thanks!

YES! Now I understand it. THANK YOU!!!

update = (e)=>{
scene.my.display = eval("" + text)
}

THIS IS NOT GOOD! The code continuously defines the function over and over again. You should run this script (including the maths of course) only ONE TIME in the console. Once the function has been defined, it will work as expected.

lololoer -- math.log returns the natural log (base e) of the argument.
math.log10 returns the log (base 10) of the argument.

It is not good because it is not good programming practice. You should only define a variable or function one time. When the variable or function continues to be defined over and over again, it eats up resources and it could cause computer lag or other undesirable things to happen. In fact, the scene crashed a number of times when I tried to make some simple changes because the script was running continuously even though Algodoo was not running. Those are some reasons why it is bad to do that.

I did try to fix the problem of the line growing wider over distance, but I was not able to figure out what causes that to happen. I did not work on the other problem of the line not working on the left side, but I will take a look at it today.

The function is intrinsic to Algodoo and so I don't believe that there is any way to see how it was coded. Why do you want to make another log function when it already exists?

lololoer - Es usted una estrella!

Good job! Even the pressure bypass safety valve works great!

This is fun!

It's a good concept, but I think this would be much more appealing if you would give the car some colors and/or textures. With it colored like ice or glass, it's pretty boring to look at.

At this point I would give it about an 8 for functionality, and a 3 or 4 for appearance. I'll hold off actually rating it to see if any changes will be made.

The PID control is stable and responsive!

Good idea, Benjii!

buildman - You copy and past it just like you would for any text on your computer: Select the text (highlight it), then press Ctrl-C keys (copy). Then click your cursor where you want to paste the text and press Ctrl-V keys (paste). Does this answer your question?

Good points.

ngphil - No specific algorithm. Just four simple math calculations that make the timing look somewhat like a musical beat. The script is in the large image box, if you wanted to take a look at it.

The mechanism seems rather shaky or unstable. It settles down some when I increase the sim frequency to 100, but the mechanism is still kind of sloppy, and it doesn't seem to function correctly. I'm sure with a little tweaking and some help from ngphil, it could become a reliable and smooth operating mechanism.

A BIG improvement! Nice job (as usual).

lololoer - You said: tar= target ending line point (app.mousepos), in this case there's not ending point.

Please explain. first you say that the ending line point is (app.mousepos), and then you say in this case there's no ending point! What do you mean by that?

Thanks guys!

lololoer - I believe it is working, but the pixels are so large that the image does not look like the original polygon. I tried making the pixels smaller and increasing their number by 4 times. The resulting image looks close to the original image but the lag is so bad that it takes 15 seconds per frame to update.

Also, the pixel located at [0.125,0.125] stays white. It does not have a gray scale, but it's not a fault of the pixel. There may be a bug in the calculation, but I'm not certain.

So, I believe it is working, but the resolution is so bad that it looks like it doesn't work!

Okay, now I understand. Thanks.

It fails to find words at the end of a sentence. For example, in the sentence "The requirements are:" it fails to find the word "are". And in the sentence "Hello , with this method you could search words / letters." It fails to find the word "letters".

You should be able to EDIT or delete your own comments. Have you tried that?

You made this up from your brain? Wow! That doesn't happen very often here on Algobox.

I don't think you understood what I said. Please try to search the text in your scene for the word "letters" (do not include quotation marks of course). I believe that your script cannot find the word "letters" because it is at the end of a sentence. Another word that the script cannot find in your text is the word "are" because it is followed by a non-letter punctuation mark.

You cheated by adding a space between the words and the periods in your text!

A good search tool should be able to find words in a sentence regardless of any punctuation marks nearby. And a user should not need to search by adding special characters such as " \ n ". Sorry, friend, but this search engine is not very good if you leave it as is.

Sorry, I know how a search engine should work, but I have no knowledge about how to program one. I think you are headed in the right direction with this one, but there are many things that need to be taken into consideration.

Just curious, why do you want to create a search engine in Algodoo? Is it just for the fun of doing it, or do you have some actual application for it?