Skip to content

Cache: addBitmapData can auto-create FrameData, fixes 1294 #1300

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 8, 2014

Conversation

pnstickne
Copy link
Contributor

  • In the "Particle Class" demo there was no explicitly-created FrameData which cause issues later on.
    This cache updates ensures that FrameData will be automatically created for any added cached bitmap data, unless such is explicitly supplied or forbidden.
  • Impact: low
    • AnimationManager.loadFrameData is called for all Sprites with BitmapData (except those with an explicit null FrameData) added to the cache

Ref. #1294

- In the "Particle Class" demo there was no explicitly-created FrameData which cause issues later on.
  This cache updates ensures that FrameData will be automatically created for any added cached bitmap data, unless such is explicitly supplied or forbidden.
- Impact: low
  - AnimationManager.loadFrameData is called for all Sprites with BitmapData (except those with an explicit null FrameData) added to the cache
photonstorm added a commit that referenced this pull request Nov 8, 2014
Cache: addBitmapData can auto-create FrameData, fixes 1294
@photonstorm photonstorm merged commit f06f784 into phaserjs:dev Nov 8, 2014
@RobertLowe
Copy link

Thanks for fixing this pnstickne.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants