|
From: Donal K. F. <don...@ma...> - 2006-11-23 09:26:16
|
Jeff Hobbs wrote: > Will Duquette wrote: >> This is exactly my point--there are uses for a tree widget >> that do *not* resemble a rich multicolumn listbox. > Like? An example is a document tree browser (e.g. the Contents tree that Windows help documentation browser presents). Each node in the tree is large enough that browsing it in a multi-column listbox would suck; I'd hate to have to horizontal-scroll through a whole HTML file. :-) I would imagine that any other time people have a tree of semi-structured information, the bolting-on of a multi-column listbox to a tree would count as a spare wheel too. (Which isn't to say that it isn't useful for a tree of structured information, of course.) BTW, if you have a tree and a table^W multi-column listbox, surely you'd want to be able to x-scroll each part independently? Otherwise you'd lose track of where you are when you're scanning across a wide table, or there would be trouble with tree nodes whose names are too wide forcing the first column to be very wide just so that you could see the end of the node labels... (Hmm, I'm not explaining that too well.) Donal. |