I am currently testing your earlier TreeView product. Later this year I plan to upgrade my test project to your latest TreeView and then purchase a license from you. So this question pertains to your newest TreeView:
I have a situation where I've implemented the checkbox feature in a fairly large tree. The user uses this tree to assign rights to each user. A necessary feature is that when one checks or unchecks a given node, all of the child nodes follow suit. I know how to do this in both client-side and server-side code. With the server-side version there is a noticeable delay (lag time) when the user sees the child nodes being checked/unchecked.
With your old treeview I could not get both client and server-side events to fire; one or the other but not both. Has this been corrected with your latest version?
In case you're wondering, there has to be server-side code for this. The TreeView in question is not in a modal dialog box but simply on the web page, along with other controls. And to keep things as flexible as possible, the user has the ability (right) to move away from the page whenever they want. So any checking/unchecking immediately has to be reflected in a Session data table.
My thinking is to fire the client-side code first, visually show the changes, but then also have the server-side code handle the behind-the-scenes stuff.
I have a situation where I've implemented the checkbox feature in a fairly large tree. The user uses this tree to assign rights to each user. A necessary feature is that when one checks or unchecks a given node, all of the child nodes follow suit. I know how to do this in both client-side and server-side code. With the server-side version there is a noticeable delay (lag time) when the user sees the child nodes being checked/unchecked.
With your old treeview I could not get both client and server-side events to fire; one or the other but not both. Has this been corrected with your latest version?
In case you're wondering, there has to be server-side code for this. The TreeView in question is not in a modal dialog box but simply on the web page, along with other controls. And to keep things as flexible as possible, the user has the ability (right) to move away from the page whenever they want. So any checking/unchecking immediately has to be reflected in a Session data table.
My thinking is to fire the client-side code first, visually show the changes, but then also have the server-side code handle the behind-the-scenes stuff.