Intersoft Community - WebTreeView - TreeView's client-side method bugs

TreeView's client-side method bugs

SAgosto — Wed, 09 Dec 2009 13:35:20 GMT

This behavior is designed in WebTreeView for performance concern. WebTreeView will not populate the Nodes object recusively during onload. It will populate the Nodes object during certain event such as expand. Or you could manually trigger it using Get("Nodes") or GetArrayNodes.

Thank you. As a workarond, I call the GetArrayNodes method to force the loading of the Nodes collection. This allows me to use the Nodes collection like other TreeView implementations. The documentation should be updated to reflect that this collection isn't loaded for performance reasons.

Thanks for the help!

TreeView's client-side method bugs

Glayaar — Fri, 04 Dec 2009 03:49:18 GMT

This behavior is designed in WebTreeView for performance concern. WebTreeView will not populate the Nodes object recusively during onload. It will populate the Nodes object during certain event such as expand. Or you could manually trigger it using Get("Nodes") or GetArrayNodes.

TreeView's client-side method bugs

SAgosto — Thu, 03 Dec 2009 10:17:21 GMT

In order to get the correct length, please use the
ISGetObject("treePortfolioNav").Nodes[0].Get("Nodes").length
The GetArrayNodes function will load all the collection to the JS object. You could manually build the collection using the Get("Nodes") function.

The only reason why the GetArrayNodes is used is to ensure that the node.Nodes collection is properly populated. Is there a timeline when this will be fixed? It's much cleaner to be able to use the node.Nodes collection instead of calling various methods.

TreeView's client-side method bugs

Glayaar — Wed, 02 Dec 2009 22:22:51 GMT

In order to get the correct length, please use the

ISGetObject("treePortfolioNav").Nodes[0].Get("Nodes").length

The GetArrayNodes function will load all the collection to the JS object. You could manually build the collection using the Get("Nodes") function.

TreeView's client-side method bugs

SAgosto — Wed, 02 Dec 2009 14:46:31 GMT

I found another bug. Similar to the page I modified above to illustrate another bug but this TreeView does not load on demand. Using the TreeView's Nodes property, only the first level exist. For example:

ISGetObject("treePortfolioNav").Nodes .length (3 is returned; Correct value)

ISGetObject("treePortfolioNav").Nodes[0].Nodes.length (0 is returned; Incorrect value)

ISGetObject("treePortfolioNav").GetArrayNodes() (38 is returned;)

ISGetObject("treePortfolioNav").Nodes[0].Nodes.length (2 is now returned; Correct value)

Why would GetArrayNodes cause the rest of the collection to "load"?

TreeView's client-side method bugs

SAgosto — Wed, 02 Dec 2009 14:43:28 GMT

EDIT: Removed

TreeView's client-side method bugs

Glayaar — Thu, 22 Oct 2009 23:38:55 GMT

You could check the Nodes.IsPopulate property to ensure whether the TreeView has completed the loading process. If it has not set the timeout to wait for the TreeView to complete its process. Here is the snippet:

function WebTreeView1_OnInitialize(ctrlId) {      AlertNodesAfterComplete();     
}
function AlertNodesAfterComplete() {
    var treeview = ISGetObject("WebTreeView1");
    if (treeview.Nodes.IsPopulate) {
        WebTreeView_GetNodes();
        WebTreeView_GetArrayNodes();
    }
    else {
        setTimeout(function() { AlertNodesAfterComplete(); }, 10);
    }
}

TreeView's client-side method bugs

SAgosto — Thu, 22 Oct 2009 09:25:23 GMT

Is this the only option? It seems like there would be a chance where 500ms isn't enough and the logic would fail.

Is there some sort of property/event that can be handled to determine when the WebTreeView is done with its initialization and the correct data would be returned?

TreeView's client-side method bugs

Glayaar — Thu, 22 Oct 2009 04:12:33 GMT

It seems you will need to use timeout function to wait for the WebTreeView to finish the initializing process to retrieve the correct value. In the attached modified sample, I use 500ms timeout to make sure the WebTreeView finish the initializing process before reporting the nodes length.

TreeView's client-side method bugs

SAgosto — Wed, 21 Oct 2009 10:03:24 GMT

Using the provided sample, Client_FundamentalAPI.aspx, in the WebTreeView sample. The GetArrayNodes return the correct information of the node in the tree view.

Did this issue also occurs in the provided sample?

I've modified the Client_FundamentalAPI.aspx file with a very simple example that shows the bugs with the above mentioned methods.

TreeView's client-side method bugs

SAgosto — Tue, 20 Oct 2009 11:23:10 GMT

The Intersoft's TreeView GetArrayNodes method contains a bug where each node is listed in the list twice. For example, a TreeView with 22 nodes returns 44 nodes from GetArrayNodes method.

What should the Intersoft's TreeView GetNodes method return? It's not listed within the 2009 R1 documentation but it exists within the online example. I get the root node twice which appears to be a bug. I'd assume all nodes would be return. Even if it returns the first node in the heirarchy, it should not be listed twice.