Algodoo

It's not working for me. I reset Algodoo and checked the code. I don't see any polygon spawning code.

I downloaded the scene again just to make sure that it still works, and it does. I also entered into the console "drawtriangle" (without the quotes) and it printed the function.

I don't see complaints from anyone else, and so I wonder what's going on here.

drawtriangle declared in root container, not in scene.my
that's why it's not saved with scene

Yours Is way better. Yours is exactly what I was trying to make.

I should know better than to declare a function only in the root scope and not declare it as scene.my (searialized), but that's what happened. The function "drawtriangle()" is now "scene.my.drawtriangle()". Thanks to kilinich for catching this!

Still not working. Opened .phz and scene.my.drawtriangle is called but not defined.

Try it now. I uploaded a new file. You should see scene.my.drawtriangle function in the console.

Nope, still not working. download 80869_Triangle_Spawner.phz and rename it to 80869_Triangle_Spawner.zip. Open the zip and then open scene.phn with Wordpad. Tell me if you see scene.my.drawtriangle defined in the code. I don't see it.

NO, I do not see the defined function! That is so weird because the scene works fine on my computer.

I defined the function in the console, and so it should work (but obviously it doesn't for everyone but me!). So, what the heck did I do wrong?

EDIT: Okay, I got it now! It just goes to show how picky Thyme is when defining functions. I originally defined scene.my.drawtriangle like this:

Scene.my.drawtriangle = (a, b, c, d)=>{
scene.my.error = false;
(a >= (b + c) || b >= (a + c) || c >= (a + b)) ? {
scene.my.error = true
} : {
x = {
((a + (c ^ 2 - b ^ 2) / a) / 2)
};
y = {
(c ^ 2 - x ^ 2) ^ (0.50000000)
};
Scene.addPolygon({
surfaces := [[[0, 0], [a, 0], [x, y]]];
color := d;
collideSet := 3;
body := 0
})
}
}

Obviously, that did not work. So I added the colon, and now it works:

Scene.my.drawtriangle := (a, b, c, d)........

OY!

Yes. OK now.

Thanks for all your help, Steve! I appreciate it very much.

Now that you have the scene functioning, you need to work on accuracy. The displayed side size is sometimes off by ~0.1 because it's not rounded up. Also a 20.0 side is off by 0.00004.

Yes, I already knew that but my focus until now has been getting the scene working. In fact, there are some invalid values that will not produce a triangle (as expected), but the error trapping routine does not display an error message. I think that's part of the same issue as the accuracy issue.

Thanks again.

Edit: I'm not going to worry about the 20.0 side being off by 0.00004! If that's true (and not your joke), then it's due to Algodoo floating point precision error, which I can't do anything about anyways (except maybe truncate everything beyond 3 decimal digits).

Regarding "which I can't do anything about", you give up too easily. I will give you a hint: In Algodoo 200*0.1 = 20.