On Fri, Oct 24, 2003 at 11:42:26AM -0700, Eugene Koontz wrote: > One drawback of this approach is that the size of the scrollbar will not > accurately reflect the size of the EntireData : the user will have no > visual cue to the actual range of the data, (unless of course I figure > out how to manually set the size of the scrollbar. :) )
This is quite a significant drawback :-/ > Does this sound like a reasonable alternative solution to the problems > that Don was having with subclassing GenericTreeModel? Well, as hacks go, yours is not the worst, but I would never accept the UI issue above in an application I shipped. For the record, Don's problem with SortedTreeModel seems to stem from a bug in PyGTK itself. If your only problem is slowness, you might want to invest some time into looking at the updated TreeView code (Kris did a lot of work on speeding it up) that should be in GTK+ CVS HEAD (I'm not sure if we have a released version with it). If the speed shows itself to be acceptable, you can look into requiring an updated version of the library, or, at worst, backporting the fix (or the entire updated widget). If even then it's too slow, you can look into hacking TreeView itself for speed, or using the [deprecated, yadda yadda] CList. Take care, -- Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331 _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
