On Sun, 16 Jan 2005 13:41:54 -0500, Thomas Mills Hinkle <[EMAIL PROTECTED]> wrote: > <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 >
The UI is for list the items from many categories, then edit or remove that item. So I put in the combo all the categories, when you select one, the TreeViee list all the items from that category so I can select an item and press a "Delete Button" or "Update Button". With a normal ComboBoxEntry I have no problem, but because of the large number of categories I use autocompletion for the combo so the user don't have to browse a big list of categories, that's why the user start typing, but as I said before, when I select an item from autocompletion's popups list, the entry's combo is update, but no changed signal is emited for the combo. I think the autocompletion's popup list should beheave as the combo's popup list. :S _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
