SPSprite Bounds - Is This Desirable?

TTStu

Hi,

I'm just scratching my head a little at this one.

Imagine an SPSprite *s1 (default x = 0, y = 0).

Then add a child, say a 200x200 SPQuad to it.

BUT... we set the quad.y to be 200.

So now we have an SPSprite with y = 0, but the height is 200.

Ok, so 200 is the height of the quad, but we placed the quad.y at 200, so surely the height of the SPSprite should be 400?

NSLog of s1.y gives 0

NSLog of s1.height gives 200

But clearly by looking at the screen, the s1 sprite takes up 400 pixels (0 + quad.y + quad.height).

Daniel

When you write "sprite.height", it's actually just a shortcut to "sprite.bounds.height" — which is one way to explain why the result is 200.

The other is that the width and height have nothing to do with the position. Just that the coordinate system starts at zero doesn't say that there's some content in that part of the sprite.

In your example, what would happen if the quad would be at y = -200? Then the height would suddenly be zero! Definitely not ideal, because there *is* some content inside the quad.