Hi Gregor, In fact begin_fill() was suggested as just an alias for fill(true) so the behavior you mention is not a big surprise.
Personally, my vote would be to fix it as you suggest and submit the patch as soon as possible - it may just be possible for it to make it into the 2.5 release. Thanks for the good wishes. The One Laptop per Child display is in the same hall as my talk and has been generating an amazing amount of interest. Cheers, Vern On 7/6/06, Vern Ceder <[EMAIL PROTECTED]> wrote: > Hi Gregor, > > In fact begin_fill() was suggested as just an alias for fill(true) so > the behavior you mention is not a big surprise. > > Personally, my vote would be to fix it as you suggest and submit the > patch as soon as possible - it may just be possible for it to make it > into the 2.5 release. > > Thanks for the good wishes. The One Laptop per Child display is in the > same hall as my talk and has been generating an amazing amount of > interest. > > Cheers, > Vern > > On 7/6/06, Gregor Lingl <[EMAIL PROTECTED]> wrote: > > > > Hi everyone!!! > > > > Rethink begin_fill() > > > > In the current version of turtle.py begin_fill behaves exactly like > > fill(True). > > That means, that a call begin_fill() does a filling if another call > > begin_fill() > > has been issued before. To see this, try: > > > > >>> from turtle import * > > >>> begin_fill() > > >>> forward(100) > > >>> left(50) > > >>> forward(100) > > >>> begin_fill() > > >>> > > > > Imho this is not very plausible. (Of course, calling begin_fill twice is > > also not > > very plausible, but may be done by beginners inadvertedly). I encountered > > this problem first in a course for teachers I gave today. > > > > I propose that begin_fill should behave differently, namely start a new > > filling (as it's stated in the docs, which are - as you see- in fact > > for this function > > incomplete) and discard the butlast call to begin_fill. If one > > really needed > > the current functionality , one could reseort ot fill(). > > > > We could still change this, as begin_fill (as well as end_fill) didn't > > exisist > > upto Python 2.4.x. It only should be decided quickly. (If you agreed, I'd > > submit a suitable patch) > > > Thanks to Gregor's submissions several bugs in the updated turtle.py > > > have been fixed *AND* the circle drawing code has been fixed so that > > > circle segments fill properly. Sincerest thanks to the turtle-meister! :) > > > > > > (And best of luck for Gregor's EuroPython talk on Wednesday.) > > > > > Many thanks! Due to certain circumstances my talk got a bit chaotic. > > However, > > Guido was among the attendees and I had the impression he and many others > > enjoyed the xturtle demonstrations and it was a very friendly > > athmosphere. So for > > my part I consider it to be a success. > > > > You, Vern, told that yuo also will have a talk tomorrow at NECC, so good > > luck > > to you also. > > > > Regards, Gregor > > > Cheers, > > > > > > > > Vern > > > > > > > > > > > > > > > > > -- > Vern Ceder > [EMAIL PROTECTED] > -- Vern Ceder [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "edupython" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/edupython -~----------~----~----~----~------~----~------~--~---
