On Sat, Dec 28, 2002 at 11:08:35AM -0800, David M. Cook wrote: > 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
OK, I figured out what's going on. When I append a new row and call treeview.set_cursor(path, viewcol, gtk.TRUE) to start editing on that cell, there is still a CellEditable widget in that column, and gtk doesn't like that. I guess it pays to pay attention to gtk assertions. So I have to do one of * prevent the user from appending a new row until editing is done. I can do this by setting an "editing" attribute in my controller (or I suppose I can just disable the "append" button), but it would be nice to have a safer way to determine if there's an open CellEditable in that column. * close the old CellEditable. I don't see any way to do this apart from creating my own CellRenderer. I solved the other problem I was having, of the CellEditable entry being drawn in the old column boundaries, by using idle_add to give the column time to resize before calling set_cursor(). Dave _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
