On Sun, Jul 13, 2008 at 12:23:29PM -0700, Alexnb wrote:
> > .
> > .
> > .
> > Alex, I'm lost as to what your current status is--what
> > you see as solved, and what questions still remain.
> > Do you see why the fragment above is unlikely to make
> > you happy? after()'s second argument names a function;,
> > it doesn't expect the coder to invoke it. Does the
> > self-scheduling in <URL:
> > http://tkinter.unpythonic.net/wiki/after > make sense?
> > How did it not serve you better to write
> >
> > root.after(100000000, sleeper)
.
.
.
> Well Thats what I said, only, it didn't help. It was for a busy bar and the
> bar would stop unless I was using the for loop with the time.sleep() in it.
> However, it would always stop at the same spot with after(), but when I used
> after(100, sleeper()) vs after(100, sleeper) the sleeper() would still stop,
> but it would go a little further down the bar track. If that makes sense.
> But I have given up on the idea for now, but thanks for your attempt to
> help!
.
.
.
When you write that you "have given up ...", does that
mean that a working busybar would not be a value to you
now?
_______________________________________________
Tkinter-discuss mailing list
Tkinter-discuss@python.org
http://mail.python.org/mailman/listinfo/tkinter-discuss
