Robert Nikander wrote: > <snip stuff about emitting signals from GenericTreeModel>
James Henstridge wrote: > > The GenericTreeModel class has a number of limitations (you just ran > into some). For 0.99.5, you probably can't do what you want. Note > that GenericTreeModel will leak lots of references (and can't really > be fixed). > > James. Well I did get it to emit signals. I have to call get_iter to get a TreeIter. Can't use tuples. But you were not kidding about it leaking references. I have been running a process overnight that has a few lists with 1000+ rows in them and 'top' reveals the memory footprint is now an obese 78 Megs. I am interested in your comment 'it can't be fixed.' I really like this toolkit -- it is so much more pleasant than trying to write GTK stuff in C! -- and I would take a hack at changing some source and seeing if I can't get a good abstract TreeModel working, but I don't want to waste my time if you have discovered that there is some reason it 'can't be done' -- some kind of essential design problem that I will run into after 5 days of hacking. Can you elaborate a little on that comment? Who is working on that code? Thanks, Rob _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk
