<snip> > > You want to connect to the change signal of the entry, not the combo > > -- that way the same action will happen no matter how the entry > > changes (typing, selecting, etc.). <snip> > I already do this, but as you said, every keystroke I made call my > filtering routing, so what I'm trying to figure out is the signal > emited from completion's popup list, so I can call > widget.emit_stop_by_name(...), update my TreeView and also update > combo's entry text. Any clue?
What is it you want your UI to do? I don't see why you would want it to behave differently if the user uses autocompletion or if they type by hand, which is the only reason I can think of that you'd need to connect to the completion event specifically. Tom _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
