1.8.4 custom variables in geom scope

[Kilinich]

If I set new variable in geom scope (from script window or from onCollide event e.this.myvar := someting)
and this variable contain big list, algodoo hang on trying display script window for a few minutes.
I think it must have kinda limit for that and simple cut exceeded text.

[Kilinich]

example:

draw box
open script menu
type in bottom edit box: "a := scene.addBox {}"

it will display all new box properties. I think just "class: box" will be enough.

[PhunWars]

You mean that if you type a long script let's say in the oncollide box it will show you just a grey box like if it isn't written anything ? Happened to mee too, editing a wrong script from that box is nearly impossible because you have to copy it and paste it on wordpad to edit it...

[Kilinich]

You mean that if you type a long script let's say in the oncollide box it will show you just a grey box like if it isn't written anything ? Happened to mee too, editing a wrong script from that box is nearly impossible because you have to copy it and paste it on wordpad to edit it...

I didn't try long script in onCollide, I usually hide it in some scene.my functions but if you open laser script menu from that scene: http://www.algodoo.com/algobox/details/49908 (it's near display)
you wil get a long Aldodoo hang and after a few minutes a picture like this:

[Someone Else]

Yeah, that's happened to me, also. Only I saw what looked like vertically mirrored and squashed menu buttons.

And what's that in the background of the picture?

[electronicboy]

never had that bug before...

Ive had one similar though, the text in the script menu box looked corrupted... Not sure if this is related, but might be.


Also, background scene is:

Sonar treasure hunting

Kilinich

Rating:
Filesize: 0.55 MB
Comments: 16
Ratings: 24