You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Very low priority until all the drawing methods are completed. Postponed in order to keep the library's implementation as simple as possible while we are still figuring everything out. This will involve refactoring quite a bit of the behind the scenes code in the codebase. We'll have to plan out what those changes should be to meet all the requirements of this feature.
The idea is that we would have an API that looks something like this:
The animations would still occur sequentially in this example (one turtle would move at a time). Ideally we would like the turtles to be able to run in multiple threads so that multiple turtles can be drawing on the screen at once.
This feature is excellent for teaching parallel and concurrent programming.
Add reset() and clear() methods to Drawing that clear all of the drawings. The turtle reset() and clear() methods only clear that turtle's drawings
Are turtles cloneable? Would clone copy the drawings of the turtle or just its current state? (Position, angle, pen, etc.)
Does dropping a turtle delete its drawings? (Answer is probably no since each turtle is just a "handle" to data represented in the renderer but still worth considering)
Turtle needs to be Send in order for each turtle to be moved into a separate thread, having Turtle be Sync is probably not desirable
Add a examples/maze_multiple example that uses multiple turtles to draw the maze concurrently
Document that wait_for_click does not work for multiple turtles because it consumes events from the global event pipe
Note that this feature has nothing to do with async. There is a separate issue (#17) open for that.
The text was updated successfully, but these errors were encountered:
A large portion of the work for this issue was completed in #173. You can use multiple turtles if you compile turtle with the unstable feature. See the documentation for more information on how to do that.
Multiple turtle support is still largely experimental and has many bugs/performance issues that need to be worked out. Feel free to experiment and report back what you find!
Very low priority until all the drawing methods are completed. Postponed in order to keep the library's implementation as simple as possible while we are still figuring everything out. This will involve refactoring quite a bit of the behind the scenes code in the codebase. We'll have to plan out what those changes should be to meet all the requirements of this feature.
The idea is that we would have an API that looks something like this:
The animations would still occur sequentially in this example (one turtle would move at a time). Ideally we would like the turtles to be able to run in multiple threads so that multiple turtles can be drawing on the screen at once.
This feature is excellent for teaching parallel and concurrent programming.
reset()
andclear()
methods toDrawing
that clear all of the drawings. The turtlereset()
andclear()
methods only clear that turtle's drawingsTurtle
needs to beSend
in order for each turtle to be moved into a separate thread, havingTurtle
beSync
is probably not desirableexamples/maze_multiple
example that uses multiple turtles to draw the maze concurrentlywait_for_click
does not work for multiple turtles because it consumes events from the global event pipeNote that this feature has nothing to do with async. There is a separate issue (#17) open for that.
The text was updated successfully, but these errors were encountered: