This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ingrid
Recipients Garrett.Grimsley, gregorlingl, ingrid
Date 2014-09-17.18:27:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1410978437.41.0.377289980068.issue21077@psf.upfronthosting.co.za>
In-reply-to
Content
This seems to be caused by a bug in TurtleScreen.update/turtle._drawturtle. When the speed is set to zero, the tracer method is used to regulate drawing circles, and when called with a positive integer, tracer calls update. Update iterates over the list of existing turtle objects and then updates them and calls _drawturtle on them, then redraws them, but doesn't draw lines or stamps so they'll get drawn over by shapes and images. I attached a snippet that shows the bug happening when you call update directly, if you switch the last line and use tracer instead the same thing happens. I think the way to fix it is to add stamps and lines to _drawturtle so I'm going to work on a patch that uses that approach.
History
Date User Action Args
2014-09-17 18:27:17ingridsetrecipients: + ingrid, gregorlingl, Garrett.Grimsley
2014-09-17 18:27:17ingridsetmessageid: <1410978437.41.0.377289980068.issue21077@psf.upfronthosting.co.za>
2014-09-17 18:27:17ingridlinkissue21077 messages
2014-09-17 18:27:17ingridcreate