Framerate Ticker and Command Line Arguments #77
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…h the --fps command line flag.
…h the --fps command line flag.
|
Further, I do know this already existed within the label. However, I felt it was more accurate to establish a more consistent and stable visual of the framerate, to allow developers to see more clearly what is occurring. The current implementation moves too rapidly to make much of it, in my opinion. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit implements a framerate ticker in the bottom left corner of the window.
It also allows for further extension of command line arguments.
I do believe this could be further refactored to use a module such as argparse, but I felt that as the goal of this project is to teach people how to code, the implementation of sys.argv was more suitable.