On Thu, 13 Sep 2001, Lionel Ulmer wrote:
> > > This is doable (just catch key_press_event and emit_stop_by_name() in the
> > > handler) but I'm not sure it would solve the problem.
> >
> > I will try to do that :-)
>
> Ok, just tried it, but it does not work exactly as expected : it works just
> fine for the PageUp / PageDown keys, but NOT on the cursor keys.
>
> Indeed, it seems that when I 'stop' the signal, it goes directly to GTK's
> navigation handling and the focus moves to the 'next' widget in its list.
I believe if you connect_after that problem could be solved; James told me
this isn't 100% accurate though.
Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 272 3330 | NMFL
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
