In just 2 threads related to this topic there are 350+ views to date. This is a big deal for a lot of people. Since this is important to me as well, I'd like to see it get solved. I suspect that somewhere over there there are some big questions that you havn't found solutions to.

 

Here is the $64 question: Can you open these problems up for discussion? Enough people are looking at this that if you started a thread listing the problems and asking for suggestions you should get more than enough viable answers, and if not, at least we would all know why this can't be implemented.

 

I guess that this is my bid for virtual mode in a tree.

 

At least it could be implemented as a semi virtual mode, where the rows that have been requested are kept around (since presumably you have to remember expanded states etc.)

 

I think this could be done in a few steps:

1. do the virtual mode as normal

2. When the virtual item gives the info on items in the tree it indicates whether or not the item has children

3. When the item is expanded a virtual record for the list of children is requested.

4. once an item has been read in, it never leaves memory until the node is collapsed or the control is destroyed. (enabling the expanded/collapsed state to be maintained.)

 

Are there any inherent problems with this design?

 

This is not a VITAL feature, but it is close. Most of the stuff in our database ought to be showed in a tree in many situations. I suspect that this is not an unusual need.