Algodoo

Good job! You obviously know a lot about Thyme scripting, and so I hope you will post more tutorials like this one.

Suggestion: In addition to showing some examples of scripts, it would be helpful if you could also include some text description of how the script works, and maybe explain when, where, and why you would use the various examples.

THANKS!

Method 1: The onClick handler of the circle updates a variable (a counter)in scene.my. The scoreboard "reads" that because it has {....} in its text attribute.

Method 2: The onClick handler of the circle updates its own counter. It also "writes" it to the scoreboard. To do that it needs the internal ref of the scoreboard. It can get that because the scoreboard writes it to scene.my. in its onSpawn handler (which is executed when the scene loads).

Method 3: The onClick handler of the circle updates its own counter. The scoreboard "reads" it from there. To do that it needs the internal ref of the circle. It can get that because the circle writes it to scene.my. in its onSpawn handler (which is executed when the scene loads).

As an alternative I could have obtained the internal ref of an entity (circle or scoreboard) by coding its geomID or entityID and calling either scene.entityByGeomID or scene.entityByID.

I am new to Algodoo and have found out most of this by trial and error.http://www.algodoo.com/algobox/theme/smilies/bonk.gif
So I have no idea when to use these methods. I was just showing what is possible. Method 1 is the easiest to understand and use.

I have seen other people call a function called "readable" and use an attribute(?) called "owner" when dealing with objects, but I have been unable to find out what they are. I would be grateful if anyone could tell me.

Thanks for the explanations!

Some time ago I was also puzzled about "readable" and "owner" and so I asked about them in the Algodoo forum. I got some answers, and they are now a little clearer to me now, but I am still a little bit puzzled about how and when to use them. Here is a link to the forum post:

http://www.algodoo.com/forum/viewtopic.php?f=13&t=10428&p=71160&hilit=readable#p71160

If you search the forum for "readable" and "owner", you will find some more posts that describe them. Some posts are useful and some are not, but I've learned some things about them through my own experimentation.

Thanks for that Xray. Silly me: I had been using Google searches without realising that the forum has its own.

I have read most of posts you indicated and found it interesting that you and other people have had exactly the same difficulties. I have also fallen into the trap of not realising that UNDO can remove code you have entered.

Thanks for your help.

Remember that all onSpawn events also called on undo so I'd rather you add condition sim.time == 0 ? {init code}:{}

Storing objects in scene.my. is very bad idea because of serialization problem in algodoo, it can't correctly store it, that's why better do it in non- _variables in objects...