On Sat, Apr 03, 2004 at 02:12:28PM +0200, Nemesis wrote: > Hmm, I think that the n.1 is the most simple, but however you have to > cicle the list and rebuild the tree, as far I can see. > I'm not sure I understood n.2,
The idea is to subclass TreeStore and override TreeStore.set/set_value (and also TreeStore.remove if you are deleting nodes) so that you save data every time set_value is called. But why persist the store, why not just keep it in memory and use TreeView.set_model to change stores? Do you really need to save the headers in between sessions? 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/
