I wanna shake him/her, very hard and at the top of my voice say 'What do you think you're doing fool?'

In the block itself create a rule if self.motion.linearVelocityY = 0 change attribute 'moving' to false. (so when the block stops moving it changes the game attribute.)

So you want to display the score (using tableCellValue(tableName,row,column) and then overlay a graphic on top of the text but have the graphic change depending on the cell value?

Yep, I see what you mean. I also know that GS loads the stuff at the top first, but if that was not working properly for him, then I suggested that he do a timer where the behaviors are separated by 0

(Quote)

Thx Socks, the snowflake looks awesome! I tried your solution for the collision line and I couldn't get it to work. The object that is falling is 40 pixels high, it starts out 40 pixels above the top

1. I'm making a tetris like game where objects randomly spawn from the top of the screen, fall to the bottom and stack. If they stack to the top, the game is over. I'm having a hard time figuring out

When x position = XXX then destroy actor and spawn a new one righthand side of the screen.

(Quote)

3) Now export you PNG 24 with transparency Layer and flag interlaced (this is optional but make the PNG more defined)

Fair enough, we'll have to disagree here, for me on the simple question of whether generating new actors through spawn and destroy impacts performance and memory usage I'd say 'no', loading those acto

(Quote)

. . . or build for iPhone4 and crop off material from the top and bottom when on iPhone5 . . .

I think it's important we don't conflate the spawing / destroy method itself with what is being spawned, of course spawning hundreds of fire balls with animations and particles and their own audio (an

my fps to 35fps. After that I switched to spawn/destroy and gained back those lost fps, but I tell you I'm still getting lags (iPad2/iPhone4s) when I'm spawning my actors, I believe it's due to their

on. Most cases these days I would spawn and destroy over recycle. Obviously there are situations you might find it more efficient from a coding standpoint but based straight off performance there's n

Yeah, it's rock solid from what I can tell, I've tried pretty much everything you can imagine to bring the device to it's knees with wanton spawning and destroying (or 'S&D' as I like to call

As far as I understand it, the idea that spawning and destroying slowly eats into memory usage is a myth left over from versions of GameSalad from a fair while back, I've done some fairly extensive te

Destroy the actor and spawn a new one at whatever size you want.

I am trying to create a menu to display a picture and it's data. I am thinking which way is better. 1)Spawn and destroy the display or 2) Use alpha to make the actor invisible (the actor would still