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
As shown in https://go-review.googlesource.com/#/c/12339/ arranger functions may need the screen dimension info. The CL work around the problem using a global var, but a better approach is to let the sprite engine provides the info it already has.
@nigeltao @crawshaw
The text was updated successfully, but these errors were encountered:
Should a paint.Event contain a config.Event? Should we do the same for touch.Event?
(Just thinking out loud...)
Sorry, something went wrong.
(I realize that that's sort of tangential to the sprite's arrangers.)
No branches or pull requests
As shown in https://go-review.googlesource.com/#/c/12339/ arranger functions may need the screen dimension info. The CL work around the problem using a global var, but a better approach is to let the sprite engine provides the info it already has.
@nigeltao @crawshaw
The text was updated successfully, but these errors were encountered: