Scene.my issues

[Chronos]

You're completely doing it wrong. I'm uploading a video of me proving my point.

...

Well?

Uploading a 900 MB file takes some time, bro.

EDIT: Bamf

[Someone Else]

Sorry, but it's you who's got it wrong. If you do that, that's exactly what will happen. But, he said that he called upon color = scene.my.blah ONLASERHIT.

Thus, my experiment was correct. And yours is not.

Then in the laser I wrote in onlaserhit ---

Code: Select all

color = scene.my.laser1color

I can only assume that the laser would be constantly hitting something, constantly refreshing itself.

[/argument]

[Chronos]

Sorry, but it's you who's got it wrong. If you do that, that's exactly what will happen. But, he said that he called upon color = scene.my.blah ONLASERHIT.

Thus, my experiment was correct. And yours is not.

Then in the laser I wrote in onlaserhit ---

Code: Select all

color = scene.my.laser1color

I can only assume that the laser would be constantly hitting something, constantly refreshing itself.

[/argument]

Oh, huh, I don't know how I missed something that important. Well now I feel a bit silly.

[Someone Else]

I only pointed it out fifteen times.
But anyway. At least we are both on the same page now.

And I am now sure that what I think is correct is actually correct.

[bozbez]

What you think is correct is very correct

[Someone Else]

What you think is correct is very correct

At least, when I think something is correct. Such is not always the case, however.

[hiltropper]

i use this braces behaviour for example when spawning circles

Code: Select all

(e)=>{
    for({scene.my.v2}, (i)=>{
        scene.addcircle({
            pos := e.pos;
            density := 5;
            color := [1, 1, 1, 1];
            colorhsva := [44, 1, 1, 1];
            radius := scene.my.v1;
            fricition := 0;
            restitution := 0;
            collideset := 35
        })
    })
}

as you can see , scene.my.v2 is given as variable ,beacuse it has to be changeable permanently
scene.my.v1 is given as "change to value once" , because if a cirle spawns ,it gets a radius and this radius cannot be changed anymore (by the way otherwise algodoo would not accept it )

[daniels220]

I don't think you need the braces around scene.my.v2—you're only actually using that value once, as a parameter in a function call (which is what for() is). Since scene.my.v2 can't change during the execution of the loop (since the loop runs in a single timestep, so no collisions/laserhits, and you aren't changing it in the inner function), you can just pass it by value.

[hiltropper]

no when you let out the braces algodoo does not accept it .it just spawns nothing so what has been said on this two sites here is important just mind when you should set braces .btw it is not changeable while the loop , but after (i am using it for a carburetor
script, circles are gasoline expansions)

[daniels220]

Works for me (Algodoo 1.8.5/Mac). Just to be clear, the code looks like:

Code: Select all

for(scene.my.v2, (i)=>{ //the spawn code })

You do need the braces after (i)=>, those define the function body.

[hiltropper]

ok for normal spawning yo are right , i thought it because of my motor with the carburetor but testet it again in general and then you can leave the braces
the braces after the assignment are normal