Improve DrawingTurtle position handling and visual bug fixes #1172
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.
Please check if the PR fulfills these requirements:
Close issues:
The DrawingTurtle app has been reworked to detect when a user accesses and changes the position variable directly (this was unhandled before). This change fixes major visual bugs that occurred when users accessed both the position variable and used the jump function. It also properly detects when polygons are closed by checking if vertices are aligned. Now, polygons can be closed due to the jump() function, due to a change in the position variable, or when the polygon is actually closed.
I've gone through and tested each and every lesson which uses the DrawingTurtle app and ensured that the correct solutions all still work. However, I can't say that I've gone through and tested every permutation of every error message. I will need some help with that.
One other thing. I've noticed that the camera seems slightly less responsive now. I'm not sure why. I don't believe anything I changed should have affected the camera.