-
Notifications
You must be signed in to change notification settings - Fork 3
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
Tim/frame rate #100
Tim/frame rate #100
Conversation
Added mouse_down(), mouse_is_pressed and mouse_up docs
Version 0.1.1
Bumped test run
v0.1.2 release
Not sure if this is the right place to put it but I was getting a key error trying to put it as property
tests different cases of trying to re-assign FRAME_RATE
FRAME_RATE is a @Property and an @ignite_global. @FRAME_RATE.setter is supposed to prevent the user from re-assigning.
…tim/frame_rate
Somehow our |
test/FrameRateTest.ipynb
Outdated
"source": [ | ||
"%%ignite\n", | ||
"\n", | ||
"def setup():\n", | ||
" size(200, 100)\n", | ||
" background(\"light blue\")\n", | ||
" FRAME_RATE = 1\n", | ||
" print(\"frame rate:\", FRAME_RATE)\n", | ||
" # this prints 1, not what I want\n" | ||
] |
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.
Please clean up tests like these. In this case, just outright delete this and make sure your other comments are ready-to-go
test/FrameRateTest.ipynb
Outdated
"source": [ | ||
"%%ignite\n", | ||
"\n", | ||
"def setup():\n", | ||
" size(200, 100)\n", | ||
" background(\"light blue\")\n", | ||
" print(\"frame rate:\", FRAME_RATE)\n", | ||
" FRAME_RATE = 10\n", | ||
" # this gives an error, FRAME_RATE is referenced before assignment" | ||
] |
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.
Same thing, delete this test
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.
We're missing docs on how to access the FRAME_RATE variable and what it does, could you please add that? Please also add a note that you should treat FRAME_RATE
as read-only and don't try re-assigning it.
Added a description of FRAME_RATE to utilities.md
Please someone have a look at this, not sure if I've done everything right. I made the already existing
FRAME_RATE
in core.py accessible to the user by making it an ignite_global. I also added a sentence to the documentation mentioning the frame rate. Closes #81