Browse Search Popular Register Upload Rules User list Login:
Search:
collideSet Reader

Image:
screenshot of the scene

Author: alasmyfoe

Group: Default

Filesize: 9.02 kB

Date added: 2015-12-24

Rating: 5

Downloads: 113

Views: 79

Comments: 4

Ratings: 1

Times favored: 0

Made with: Algodoo v2.1.0

Tags:

Scene tag

Some people are so lazy that they can't even click on script menu, and look for collideSet.
I made this to solve that.
I also want to continue practice scripting.
If there are any improvements on can make, tell me:D
Last edited at 2015/12/24 18:31:56 by alasmyfoe
Please log in to rate this scene
edit
Similar scenes
Title: Attraction engine
Rating: 5
Filesize: 19.11 kB
Downloads: 317
Comments: 0
Ratings: 1
Date added: 2009/06/26 04:29:11
Made with: Phun
Rating: rated 5
download
Title: "Laser" CD Reader
Rating: 6
Filesize: 0.98 MB
Downloads: 1222
Comments: 2
Ratings: 3
Date added: 2009/08/31 03:41:35
Made with: Phun
Rating: rated 6
download
Title: Card Reader
Rating: 5
Filesize: 56.78 kB
Downloads: 883
Comments: 0
Ratings: 1
Date added: 2009/07/08 02:45:02
Made with: Phun
Rating: rated 5
download
Title: more scripting v2
Rating: 5
Filesize: 5.2 kB
Downloads: 244
Comments: 0
Ratings: 1
Date added: 2010/02/18 03:26:36
Made with: Phun
Rating: rated 5
download
Title: collideset changing demo
Rating: 5
Filesize: 13.88 kB
Downloads: 160
Comments: 0
Ratings: 1
Date added: 2014/06/04 23:43:19
Made with: Algodoo v2.1.0
Rating: rated 5
download
Title: I-Reader Probe
Rating: 5
Filesize: 24.06 kB
Downloads: 359
Comments: 0
Ratings: 1
Date added: 2009/11/28 19:57:24
Made with: Algodoo before v1.8.5
Rating: rated 5
download
well you could do it way simpler xD

Oncollide: (e)=>{e.other.text = "" + e.other.oncollide}
Ok, thanks! But im gonna leave it the way it is:D
There's an importand fact you need to know: all "events" (code that starts with (e)=>{) own the e inside the () as a parameter, keeping tract of all data of the event using a view variables and 1-2 references that give you the ability to interact with the participating objects(usually this and other/geom). When you want to access any variable, just call that variable using the reference, i.e. e.other.text (the text of the "other" object recorded in e)
This works with any event, just that the onLaserHit event uses e.geom instead of e.other, and that onCollide is the only event that uses e.other . You could also access the executing objects var's directly by just writing the name(i.e. pos = [2,5])
Remember to ask me via forum about thyme, then I can teach you even before you upload a scene:D
You know why I am actually so eager to help ya? You are the first person that i've met who used to make algocamps and marble stuff, but finally started dooing other kinds of scenes after realizing how many of these scenes exist >.<

If you keep it like that, with as few camp and marble scenes as possible, you could become something really cool, especially if you keep improving in your scripting ability.

If you check my very first scenes, You will notice that even I started "small". It may seem that my very first scenes were super-duper-advanced, but you must remember I already scripted before even uploading my first scene. Keep taking steps, and everytime your new skills enable you to do something really cool, try it and make something special out of it. This way you quickly get a lot of quality scene with a lot of variety.