DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=bptSFGuJHFUKqpVpPyTmEzF639oBtVG9VsPceiEvXZjWxtrgKjSSJVXTVOfwlFXg16uFZ9dqoRnigFSO7k7/2khpV/dOCRpimdh4LHIE1rwzvALIdLVXHz+IYQuHHUbZ6Eslss2bYra19pZQSBgMyaHZw0MukDk0gIfrX280o/Q=
Message-ID: <6b8a91420602070431k2e06b8d6n at mail.gmail.com>
Date: Tue, 7 Feb 2006 13:31:23 +0100
From: Remi Vanicat <remi.vanicat at gmail.com>
To: David MENTRE <dmentre at linux-france.org>
Subject: Re: How to use a progress bar in a program loop
Cc: Olivier Andrieu <oandrieu at nerim.net>, lablgtk at math.nagoya-u.ac.jp,
        demexp-dev@nongnu.org
In-Reply-To: <87oe1k6tmt.fsf at linux-france.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
References: <87vevurlyt.fsf at linux-france.org>
	 <17382.10638.543279.353714@karryall.dnsalias.org>
	 <87oe1k6tmt.fsf@linux-france.org>
Content-Transfer-Encoding: 8bit

2006/2/6, David MENTRE <dmentre at linux-france.org>:
>
> Well. In fact the lengthy update comes from network access time. I
> wanted to avoid thread issues for my relatively simple client
> application (I already have enough issues without chasing thread bugs
> ;). Maybe one day I'll redesign it with the GUI on one side and all the
> network/computation code on the other side, to allow for asynchronous
> behavior.

Note that by using equeue and the method to use equeue in lablgtk you
can make the gtk event loop to take care of yours network access time
(that is you can write your program with callback that are called when
one can read/write to the network)