On Tue, Dec 02, 2003 at 07:50:43PM +, Jean-Baptiste Cazier wrote:
> After further investigation and tests it turns out that the costing
> event is the connection to expose_event of the DrawingArea, not the
> mouse_motion, nor the resizing of the window.
> self.area.connect("expose-event", self
x27;t use them,
> i don't know how some code can do tasks...
>
> I'm a bit confused now, and with much tasks here at work..
> ..i'll try to write later..
>
> -Original Message-
> From: Jean-Baptiste Cazier <[EMAIL PROTECTED]>
> To: &quo
On Mon, Dec 01, 2003 at 05:22:18PM +, Jean-Baptiste Cazier wrote:
> Could you please tell me if this is a normal behaviour or otherwise
> help finding where this comes from.
Shouldn't be the case; maybe you have a timeout handler that's eating up
your CPU, or if you're using threads, a runaway
Sæll !
I have developped a nice, but large program with a graphical interface with pygtk.
However it is extremly CPU consuming (95%) even when idle or when the window is
minimized
I have indeed a lot of "connect" set-up but could this be due to something else ?
Could you please tell me if this
