On Tue, 18 Feb 2003 20:45:23 +0800, James Henstridge <[EMAIL PROTECTED]> wrote: > >.... I have had to use the > >"cursor_changed" signal which emits two signal on the first click because > >no row was initially selected. > > With the new tree widget, the selection is abstracted as a separate > object, which can be obtained with: > selection = treeview.get_selection() > > (I think the original reason for this was to allow two views of one > model to share a selection). > For single selection tree views, you can call selection.get_selected() > to retrieve the selected row. For notification of changes to the > selection, connect to the selection's "changed" signal.
I have tried your suggestion and still don't understand why I'm getting two signals. Upon starting, no selection is made to the "selection" then after clicking any row (other than the first row) the changed signal is emitted twice, once for the first row (even though that was never selected then again for the selected row). For the extremely curious, this is the problem app.: http://unihedron.com/projects/gonvert/gonvert.php Thanks in advance. -- Anthony Tekatch _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
