Welcome, Guest

Want to take part in these discussions? Sign in if you have an account, or apply for one below

• Forgot your password?
• Apply for membership

1. • CommentAuthorKoj
   • CommentTimeApr 15th 2009

    
   Hey there,
   
   It seems as though when stop() is called on an Emitter that uses internal ticks FrameUpdater stops listening to UpdateEvents when it is actually listening to ENTER_FRAME events. The result of this is that FrameUpdater continues to make calls every frame even after an emitter is stopped, its renderer is removed from the display list and both are set to null. Could you please fix this so that FrameUpdater stops making unnecessary calls after an emitter is stopped? Thank you.
2. • CommentAuthorRichard
   • CommentTimeApr 16th 2009

    
   When you call stop on the emitter, the emitter stops listening to the update event from the FrameUpdater, which is correct. The FrameUpdater continues to listen to the enterFrame event and dispatch update events because other emitters may be listening for them. There's no bug in this.
   
   However, I see that it could be more efficient by using reference counting and stopping the enterFrame listener in the FrameUpdater if there are no update event listeners. Since it doesn't break anything and the cost of the single enterFrame listener is small, this is not a high priority change. I will add it to the list of nice to have changes and try to get it in the 2.1 release, whenever I have time to finish that.
3. • CommentAuthorKoj
   • CommentTimeApr 17th 2009

    
   Thanks you much.