Sæl !
I tried my example but without any sucess as the area is not suppose to have that
method !
Traceback (most recent call last):
File ./ldraw2.py, line 2884, in area_expose_cb
area.window.signal_handler_block(self.signal_id)
AttributeError: 'gtk.gdk.Window' object has no attribute
On Mon, Dec 08, 2003 at 09:50:30AM +, Jean-Baptiste Cazier wrote:
I tried my example but without any sucess as the area is not suppose to have that
method !
Traceback (most recent call last):
File ./ldraw2.py, line 2884, in area_expose_cb
Sael !
Thanks again for the interest you give to my development :)
As I stated in my e-mail I started with the area itself without sucess.
Then I tried with its associated window, but none of them have the block event
installed
But I realise I put the wrong output line in my e-mail :(
area
On Mon, Dec 08, 2003 at 12:47:39PM +, Jean-Baptiste Cazier wrote:
But I realise I put the wrong output line in my e-mail :(
area expose cb GdkRectangle at 0x81fa890 0 __main__.DrawingArea instance at
0x863e97c GdkEvent at 0xbfffdaa0 gtk.DrawingArea object (GtkDrawingArea) at
0x8513c04
Indeed I found there the handler_block command which actually exists
However it did not solve my problem at all
I even tried to the more direct disconnect at start and re-connection at the end of
the routine but without further success
I am quite disappointed
I simply do not understand why the
On Mon, Dec 08, 2003 at 01:24:41PM +, 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.
A Sex, 2003-12-05 às 18:13, Jean-Baptiste Cazier escreveu:
hi !
After further investigation it seems that the routine called by my expose_event
signal is generating itself new expose_event...
To avoid that effect I would like to block the signal when entering the routine and
unblock it
On Monday 08 December 2003 10:37 am, Gustavo J. A. M. Carneiro wrote:
. This would be a Bad Idea (TM)!
Anyway, an alternative to signal handler blocking, which doesn't seem
to be working (I read down the thread), would be a simple trick of
locking:
def area_expose_cb(self, area,
On Fri, Dec 05, 2003 at 06:13:06PM +, Jean-Baptiste Cazier wrote:
After further investigation it seems that the routine called by my
expose_event signal is generating itself new expose_event...
That's definitely not a good thing :-)
To avoid that effect I would like to block the signal
