Re: Execute an external program and progress bar

[Gérard Milmeister <gemi bluewin ch>]

On Mon, 2003-04-28 at 15:27, Sean Middleditch wrote:
> If it's going to take more than a second or three, it's better to use
> the progress dialog.  Hourglasses only tell you that the app _should_ be
> busy, not that it actually is - i.e., you can't tell if an app is locked
> up, and impatient people might just assume it is.
> 
> I think the HIG covers the do's and dont's of using progress
> bars/dialogs properly, I'd heavily suggest reading it when doing any
> GNOME devel work.  ^,^

I implemented the thing using gtk_timeout_add, and it seems to work
quite nicely (it may possibly not quite robust though). 
What would be a good timeout value? I currently use 100ms.
When I start the process I use gtk_set_sensitive to disable interaction
with the main window. However I would like to have a stop button on the
toolbar, and when I disable the top widget, this button will stay
disabled and I cannot enable it alone. Must I then use gtk_set_sensitive
on every widget in the main window except the stop button, or is there
a better solution?

Regards

-- 
Gérard Milmeister
Tannenrauchstrasse 35
8038 Zürich
gemi bluewin ch