I've been banging my head against some real weirdness with implementing my own TreeModel with editable cells, particularly with editableCells showing up where they shouldn't, even overlapping, and also problems with selections. I made a bug report on one of the minor problems I've been having (EditableCells offset to the left):
http://bugzilla.gnome.org/show_bug.cgi?id=101748 I did a google search and found this old message http://www.daa.com.au/pipermail/pygtk/2001-December/002227.html which seems to indicate that there are fundamental problems with the GenericTreeModel (but that was a year ago). Should I keep trying to get it to work? However, I definitely can't say that my code isn't at fault as I don't understand the API completely, particulary exactly when some signals need to be emitted (row_changed, row_has_child_toggled, row_inserted). I'll try to bang together a simplified python test program for this that might demonstrate the problems. Dave Cook _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
