Olivier Biot

@NemoStein adding the following getter/setter to the NineSliceSprite class seems to do the trick on my side : ````javascript /** * width of the NineSliceSprite * @public * @type {number}...

I committed the changes, maybe easier to pull the latest changes on your side : https://github.com/melonjs/melonJS/commit/b0ee2b274e1e87fc10fad3772e4494383e4ecd10 let me know, once you confirm you are good with it I'll publish the...

oh I see...... honestly I don't know how to fix this one quickly... the thing is that the sprite resizing/scaling feature rely on [Matrix transformation](https://github.com/melonjs/melonJS/blob/master/src/renderable/renderable.js#L570) to display the final sprite...

ok, I'll keep it like this for now and go on with the 13.1 release. I will see later how we can properly implement this. I must admit though I...

13.1.0 was just [released](https://github.com/melonjs/melonJS/releases/tag/13.1.0) ! Followed by a quick 13.1.1 fix but just for date and change tracking :)

@L1lith making some progress here, with now `game` being an instance of `Application` (a new class). Unfortunately this not yet though possible to create a different Application instance, as references...

it's a good suggestion indeed, we have a FAQ [here](https://github.com/melonjs/melonJS/wiki/Frequently-Asked-Questions) but having it indeed in the doc would make it "easier" to see, and to contribute @ShukantPal any suggestion on...

oh that's 2 times interesting : 1. we can indeed have a FAQ "only" repository, where it's easier for user to contribute, and have it totally integrated with the documentation...

see also #709 , this should then be extended to all shapes constructor. (can come as a second step though)

another solution to this, that we discussed in the past as well, would be to reimplement me.Rect as a pure "box" object, that would then only be used for bounding...