Correct implementation of no_loop() #176
Merged
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.
Closes #175
#158 had problem of draw() being called two times if we use no_loop() inside draw() function, which was fixed by a PR by me but it led to #175, that is no_loop() when used in setup() don't call draw() once, as per Processing original documentation
This PR calls draw() once when used in setup() and don't call draw() again if no_loop() is used in draw() again, also I have tested the frame_count for each call and frame_count is being incremented as described by @jeremydouglass in #162 comments,
The issue #158 and #162 is taken care by this PR , I have tested the code for loop(), no_loop(), redraw() for both in setup() and draw() functions and some other codes from examples of p5
But you can test it for some other scenarios too :)
PS : size() when used in setup() along with no_loop() is still buggy, but I don't think it is happening due to no_loop()