Parameters from Tiled Json

[Climbus]

Hi all

 

I'm using Phaser with json maps created by Tiled.

 

In Phaser docs i found info that i can use parameters: http://docs.phaser.io/Phaser.Tilemap.html#createFromObjects. 

 

I tested it and it is not working corectly with maps generated in Tiled. I attached exeample.

 

Tiled puts all parameters values in quotes: "body.velocity.x":"10". In that case object goes fast to maxVelocity.

When i remove quotes manualy, object is moving with given velocity.

 

In my example you can comment line 7 and uncomment line 8 in main.js file to check two cases.

 

Is this Phaser bug or i'm doing something worong?

 

Climbus

TestCreateFromObject.zip

[wayfinder]

I think Tiled's output is interpreted as a string, so you might have luck with trying parseInt()?

[Climbus]

I think Tiled's output is interpreted as a string, so you might have luck with trying parseInt()?

 

I'm using Phaser internal function so i cant add parseInt in code responsible for setting parameters.

 

I think that code dont't evaluate this string so i cant put "parseInt(10)" to Tiled.

[rich]

Hmm good point. I'm not sure there is an easy fix for this. If I parseInt every value then it will break string / object based properties. If I leave it as is, some properties will convert from strings to integers fine, and others won't. I'm not sure there is an easy solution for this.

[Climbus]

Hmm good point. I'm not sure there is an easy fix for this. If I parseInt every value then it will break string / object based properties. If I leave it as is, some properties will convert from strings to integers fine, and others won't. I'm not sure there is an easy solution for this.

 

Maybe Point object can have setter for x and y values. I dont know is it posible in JS.

[Climbus]

Maybe Point object can have setter for x and y values. I dont know is it posible in JS.

 

Something like this:

a = {     set x(val) {         this._x = parseInt(val);    },    get x() {         return this._x;     }}a.x = "aaa"a.x//NaNa.x = "123"a.x//123

[rich]

It would need to be parseFloat, but even so the thought of doing a parseFloat on every single Point object, every single time the x or y values change, is quite terrifying to be honest.