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.

Sign up for GitHub

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

Jump to bottom

Broken test for Screen #52

Open
SinGarTheGoat opened this issue Feb 10, 2017 · 1 comment
Open

Broken test for Screen #52

SinGarTheGoat opened this issue Feb 10, 2017 · 1 comment

Comments

@SinGarTheGoat
Copy link

There are some variable naming conflicts (p instead of pixel, for example) that cause Ruby errors.
@dawsonc623
Copy link
Contributor

FYI to anyone looking at this: I have this on my to-fix list, and I will get to it very soon.

@cyle-dawson-bloc cyle-dawson-bloc mentioned this issue Feb 28, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dawsonc623 @SinGarTheGoat