On Mon, Dec 08, 2003 at 01:24:41PM +0000, Jean-Baptiste Cazier wrote:
> Indeed I found there the handler_block command which actually exists
> However it did not solve my problem at all
Hmm. Do you mean that even with handler_block() your callback is
triggered by an expose-event? That's quite odd. Could it be that some
other signal is triggering it too?
> I even tried to the more direct disconnect at start and re-connection
> at the end of the routine but without further success
Are you *sure* you're running into a recursion here? It now sounds more
like an emission that you're generating. If that's the case, what may be
looking for an emit_stop_by_name("expose-event').
> I am quite disappointed
Take some time into studying the signal dynamics for your case, it's
normally not too complex but can be hard to grasp at first.
> I simply do not understand why the modification of the font makes a
> call to this routine self.area.modify_font(font_desc)
Hmmm, what do you mean by this?
Take care,
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
