How to completely remove sprite? [solved]

GameOver

Hi everyone! I have here a question...

Sprite has a event handlers like this:

function mySpriteClass:init() self:addEventListener(Event.ADDED_TO_STAGE, self.onAddedToStage, self) self:addEventListener(Event.REMOVED_FROM_STAGE, self.onRemovedFromStage, self) end   function mySpriteClass:onAddedToStage() self:addEventListener(Event.ENTER_FRAME, self.onEnterFrame, self) end   function mySpriteClass:onRemovedFromStage() print("check for removed") self:removeEventListener(Event.ENTER_FRAME, self.onEnterFrame, self) end   function mySpriteClass:onEnterFrame() print("do somethimg") end

After performing

stage:removeChild(mySprite)

sprite disappears form screen well and the text "check for removed" printed, but sprite still remains in memory. So the

mySpriteClass:onEnterFrame()

will continue to execute end "do somethimg" continues printing.


How to completely remove sprite from memory?

SinisterSoft

mySprite=nil ?

GameOver

It does not help!

So I do check like this after performing stage:removeChild(mySprite)

print (type (mySprite))

I getting a "nil". But the code in the onEnterFrame handler will continue to execute!

SinisterSoft

how about mySprite:removeEventListener(Event.ENTER_FRAME,mySprite.onEnterFrame,mySprite)

before you remove it?

GameOver

Looks like I understood what was happening.
I developed mySpriteClass with ZeroBraneIDE in live coding mode.
Even a full stop and restart Gideros Player did not solve the problem.
But when I close ZeroBrane and restart again - everything ran as it should :-)
Looks like a ZeroBrane bug, this whole hour blown my brain!

Thanks for the help anyway!

john26

I think this is a feature of Gideros, though. In Gideros, if a sprite is removed from stage and nilled out (ie awaiting garbage collection) it can still receive ENTER_FRAME events. I've never understood why this is the case as it seems to cause problems and I can't think of any obvious advantage...? The "problem" (if such it is) applies only to ENTER_FRAME events, not touch events etc.

SinisterSoft

I never add an enter_frame to sprites myself so have never encountered this (luckily).

Sounds like a bug.

ar2rsawseen

@john26 is right, but in this situation he explicitly removed the even listener, so it should have been removed and stopped running.

john26

@SinisterSoft, I'm the same, I only have one ENTER_FRAME attached to the stage which does all the updating. But lots of people use an OOP approach where you have ENTER_FRAMEs attached to many sprites which may go on firing even after the sprite has been removed. The solution seems to be to add lots of removeEventListener calls which shouldn't really be necessary IMO...

I'd love to know why it was done this way? Is there any advantage?

MoKaLux

Curious guys about this one, is it still the case today?