onIdle

[standardtoaster]

onIdle would be pretty much the exact opposite of onCollide. If we had onIdle then we would be able to have noncolliding parts have scripts that are running all the time and we would be able to have a script that runs all the time but "pauses" when something hits it and then "resumes" when nothing is hitting it. Do you get what I mean?

[Torpedo]

There is essentially a way of doing this. If you have a part where one laser consistantly hits it, and then apply another laser, the laser that hit it lasts code seems to end up taking presidence over the last piece.

I cant remember exactly how it worked but i used such an idea in my seven segment display, i think it was mainly for color change. however, if you applied a check to the color of that box, you have a positive and negetive occurance from it.

[standardtoaster]

There is essentially a way of doing this. If you have a part where one laser consistantly hits it, and then apply another laser, the laser that hit it lasts code seems to end up taking presidence over the last piece.

I cant remember exactly how it worked but i used such an idea in my seven segment display, i think it was mainly for color change. however, if you applied a check to the color of that box, you have a positive and negetive occurance from it.

Yes, but having onIdle would make scripting noncolliding objects and the like a hell of a lot easier.

[Laraso]

... have scripts that are running all the time ...

But then someone will end up accidentally, while working on their scene, putting a spawn code in the onIdle box that was meant for the onCollide box, while working on a really big giant important scene of awesomeness. Algodoo will then crash, and then every time they try opening Algodoo back up again it will load the onExitSave scene and Algodoo will just end up crashing again, they will have to delete the scene to get Algodoo running again. Then said person will come to these forums and complain about how easy it is to get onIdle and onCollide mixed up, and will then fight to have onIdle abolished.

Or, someone could create something really awesome with this type of thing, and you will be praised for suggesting this.

Either way, I support.

[standardtoaster]

... have scripts that are running all the time ...

But then someone will end up accidentally, while working on their scene, putting a spawn code in the onIdle box that was meant for the onCollide box, while working on a really big giant important scene of awesomeness. Algodoo will then crash, and then every time they try opening Algodoo back up again it will load the onExitSave scene and Algodoo will just end up crashing again, they will have to delete the scene to get Algodoo running again. Then said person will come to these forums and complain about how easy it is to get onIdle and onCollide mixed up, and will then fight to have onIdle abolished.

Or, someone could create something really awesome with this type of thing, and you will be praised for suggesting this.

Either way, I support.

Your first argument is basically the same thing as saying that onHitByLaser is to easily confused with onCollide. If that's the case then just copy and paste the script from one place to another. Either way, thanks for the support. ;D

[Laraso]

Your first argument is basically the same thing as saying that onHitByLaser is to easily confused with onCollide. ... Either way, thanks for the support. ;D

Well... Someone could confuse the two, but then it would only screw up everything if it got hit by a laser. And the chances of that happening before someone has time to realize the problem then fix it aren't very high I don't think.

But with onIdle, scripts are running all the time, everytime!

And your welcome. I'm slowly getting ideas on a few things I could make with this.

[Sonic]

Won't onIdle cause a hell of a lot of lag?

[RA2lover]

not if you set a refresh timer in it.

also,

IN AN EFFORT TO RAISE MY POST COUNT

support.

[niffirg1]

Supported

[Versieon]

I do think this would be usefull. support

[Fujitsu]

I've actually run into a need for this many, many, many times.

[Chronos]

IN AN EFFORT TO RAISE MY POST COUNT

support.

ditto (to both those )

[Versieon]

Now that I think about it, it would probobly be more usefull if it was an "onalways" script box. Tht way you could have things running all the time and able to collide or have it function like onidle. That way we could have both functions it one script area instead of just onidle

[KarateBrot]

After Ivanlul's question about this kind of thing I tried to make a solution for it and here it is:
http://www.algodoo.com/forum/viewtopic.php?f=13&t=2136
I just posted it here in case that anyone is still interested in using something like onIdle

Now that I think about it, it would probobly be more usefull if it was an "onalways" script box. Tht way you could have things running all the time and able to collide or have it function like onidle. That way we could have both functions it one script area instead of just onidle

You can also do this with the code

[Matten]

A while ago I was creating a scene. But I needed to make a loop for spawned movable objects. I couldn't find a way to solve this, but with an onIdle/loop script it would! Support!

[Dakta]

Uhm... To make something execute all the time, follow KarateBrot's link to the howto.

[Rrobba]

This could be useful in certain situations, but not all. Anyway I'll support because it could come in handy.

[Matten]

Uhm... To make something execute all the time, follow KarateBrot's link to the howto.

I mean that the spawned objects need a loop, and with Karatebrot's way I would have a lot of script. With a loop script it would be very easy

[Dakta]

Admittedly yes, but I still say that implementing every single user requested feature is a stupid effort that leaves the software with too many things to reasonably support.

[fox11trot]

well just to add, an object's zdepth (objects in front of other objects) determines the priority over other scripts

so if you have too lasers both doing a script, the one that is on top of the other (overlapping) will take script priority


I support this though

[Mr_Stabby]

i only like it if it contains a refresh timer limit thingy coz otherwise it would be a lag monster