I’ve found some behaviour with nested containers that I think might be a bug, but it’s hard to know for sure.
If you create a container at 0,0 and add a sprite (say, 50 x 50px) to it, its bounds change to incorporate the sprite. Then if you move the container (with
setX(100) for instance) then the bounds change to show the new position. (
x:100, y:0, width:50, height:50 ) All good.
If you do this with a nested container, (add a sprite to child container, add container to the parent container, then call
setX(100) on the parent) instead of the position changing it simply adds to the dimensions of the container - so you end up with
x:0, y:0, width:150, height:50 .
Is this desired behaviour? I have a pen here: https://codepen.io/garystanton/pen/KjrmMe