-
Notifications
You must be signed in to change notification settings - Fork 26
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
refactor: Don't use static for Distance and Collision #92
Conversation
boxTest.initialize(); | ||
boxTest.initializeAnimation(); | ||
boxTest.runAnimation(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since we always call the same 3 methods, shouldn't Demo
expose a helper for that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, there are looots of fixes to do here, but this was just a minor side fix in the PR (to remove static main
)
Particles() | ||
..initialize() | ||
..initializeAnimation() | ||
..runAnimation(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
different style, same purpose?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
This removes the use of
static
forCollision
andDistance
so that multiple worlds can be used simultaneously and old stuff is GCed properly.Checklist
fix:
,feat:
,docs:
etc).docs
and added dartdoc comments with///
.examples
.Breaking Change
Related Issues