> > I have created a custom tree model, derived from GenericTreeModel. I use > > text strings as iters for the model. This is working well. When I get > > the current selection, I get the string that I was using as an iter. > > > > model = MyModel() > > tree.set_model(model) > > selection = tree.get_selection() > > > > return_is_string = selection.get_selected() > > I don't see how that works, it sounds like a fortuitous bug. In C, a > TreeIter is an opaque structure. You should still have to do a get_value to > get an actual usable value. > > Dave Cook
Actually, every example shows using python objects, tuples, or strings as iters. If you look at the treemodel.py demo shipped with pygtk, it uses tuples as iters. Pygtk does not allow you to instantiate TreeIters, or derive classes from a TreeIter. It seems the preferred method is to you python objects. This seems to work with everything except the TreeSortModel. Don -- Don Allingham <[EMAIL PROTECTED]> GRAMPS - Open Source Genealogy _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
