-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Maik Hertha wrote:
> >But, if the default handler do so, why I can have a
> >w.connect_after('button_press_event', cb ) and the signal is
> triggered
> >for middle and right button pressed signals an not for the
> left button
> >pressed signal (tested with a clist)?
> >
> Because the default handler for button_press_event on
> GtkCList claims to
> have handled button-1 events, but not button-2 or button-3 events.
>
> >
> >:: >Why did we have to do it back in GTK 1.2?
> >:: >
> >:: Because 1.2 didn't use the above accumulator.
> >Hm, seems to me that some logic have to change if code is ported from
> >1.2 to 2.0. This makes the event propagation very hard to
> design. If I
> >want an action on a double-click at a (clist)row I have to
> do a lot of
> >extra work in 2.0. There are some other solutions?
> >
> >
> Really? Can't you just use connect() and return True when a double
> click is performed (event.type == gtk.gdk._2BUTTON_PRESS)?
>
Then I need a little assistance. The current situation is:
- - the double-click propagates a button.clicked() signal to raise a dialog-window
- - the dialog-window pops up and is transient to the parent-window.
At this point I get a X-Server deadlock. This could only be solved with
ctrl-alt-backsp.
I mention that if the click-signal of the button is triggered, the function never
returns
while the dialog is up. Yes, the dialog would create its own mainloop. In 1.2 this
problem
was solved with a w.connect_after(). How to do in 2.0? I think starting an extra
thread is
a little bit beyond the goal.
Thank you for your help.
Regards --maik./
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
iD8DBQE+g/npbd3QGXGos6ERAuckAJ9gzYmfboTOKntQr0f4dVQvH/hS1ACdEd2n
0PSKdLIinal/D/k5Izpdw54=
=bXxS
-----END PGP SIGNATURE-----
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
