Cleaning up BaseTexture Destroy

[mattdesl]

Just noticed that we are now removing the Image reference from the base texture cache on destroy. This is good (we use this in our own fork, and it caused a big boost on mobile performance). But in my testing I've noticed that the "src" attribute of Image will not always return the exact string you set it earlier. For example, it may get appended with the domain (i.e. "http://localhost/"). This leads to a problem where the BaseTexture is still not deleted correctly.

This pull request adds three things:

• It fixes this issue by storing the imageURL string for later deletion.
• It does not call drawImage if the baseTexture's source is null.
• It adds removeAllEventListeners to EventTarget. This was useful in our game where we are loading and unloading textures on the fly, and relying on AssetLoader's "onComplete" event.

We are not unloading textures when WebGL is active, so that path may need some further testing.

P.S. What is with "dev_simple_batch" branch? Is this the new dev branch going forward?

[mattdesl]

Another issue just cropped up in our game regarding deleting base textures and sprite sheets. It was causing images not to be re-loaded.

When a sprite sheet is loaded, it gets added to the TextureCache. This happens when onJSONLoaded creates a new ImageLoader. So BaseTexture.destroy() should really be deleting the entry from the TextureCache, as well as BaseTextureGame.

[englercj]

Looks good to me! Thanks!

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.