Jon Nelson wrote:
> On Mon, 25 Mar 2002 17:01:25 +0200
> "Lior Kesos" <[EMAIL PROTECTED]> wrote:
> I think what you are hitting is the same thing I hit a while back -
> things are too piled up for your change to be displayed. It's the
> same problem with progressbars. They work great when trying one
> out for a sample, but if what you are doing locks gtk (I don't
> mean lock up just lock as in mutex) then you have no luck. Here's
> how I did it:
>
> (inside a function)
>
> myProgressBar.pbar.set_value(new_value)
> while gtk.events_pending():
> gtk.mainiteration()
>
> It works for me. Not sure if it is the "right" thing to do, though.
> When I call gtk.mainiteration() I can almost here the "kerchunk".
>
I'm a pretty new to gtk - what's the difference between
gtk.mainiteration to gtk.mainloop and
what happens during the events_pending - haven't found it in pydoc yet
(off to google I guess ...).
--
Lior Kesos , [EMAIL PROTECTED]
Aduva re.search("meaning",self)
============================
KISS - Keep It Simple Stupid.
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
