Treeviews & Folders

The issue is the time it takes to read the datastore and create each individual node in a treeview.

The default behavior is to read every single item at the current level +
    every single item at the level below the current one +
            every single item at every level below that level +
                and so on until the data has been read down to the last row.

Meanwhile, all we usually want is to get to the current folder. We usually have no need to go below the level we seek.

That's why I suggested LIMITS be placed on both object creation functions. Both a LEVEL limit and a NODE limit are reasonable and would be very useful.


Olan

Marcos -

The exact same thing happens when you create a treeview that has many, MANY nodes - it takes forever to build the structure. Once the structure has been created, it will be painted.

One answer is to find a folder with fewer sub-folders, then code your way to the correct folder if the parent folder is the one you want.

In my own code, I've implemented a LIMIT on the treeview creation that stops at a set number, then display a query to the user: "1500 rows have been retrieved. Continue retrieving data? Y/N". If the user says NO then I paint the treeview. You might be able to do something like that.

~~~~~~~~~~~

I definitely think that some kind of LIMIT parameter needs to be on any object that gets, reads, or builds something that is required to wait on fun-units;i.e. sub-nodes or dub-folders. JMHO.


Olan

If you delete the thousands of files and leave just a few files in the same folder on the environment that has the problem, does the problem go away?  Basically, I'm suggesting a troubleshooting step to see if really the problem is the amount of files.

Also, have you tried compiling your app as a 64-bit .EXE and seeing if it has the same problem?

The problem is the network drives. Local folders are working ok.