Skip to content
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

Better onUpdate paradigm #22

Closed
DeviateFish opened this issue Sep 21, 2015 · 1 comment
Closed

Better onUpdate paradigm #22

DeviateFish opened this issue Sep 21, 2015 · 1 comment
Assignees

Comments

@DeviateFish
Copy link
Owner

Instead of a single callback for onUpdate, make this an event that can be subscribed to, perhaps.

i.e. drawable.on('update', doThing);

Also do away with the notion of "return false means get rid of this drawable". Make removing/destroying a different process.

@DeviateFish
Copy link
Owner Author

Done in #26

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

No branches or pull requests

1 participant