I have a specific question, though one which might benefit others getting started with your treeview control. Here's the main part of a web page I'm building:
http://mwtech.com/downloads/public/StockMuckEditor_Capture.JPG
The treeview on the left is used to navigate down to a specific record. Once a bottommost node is reached the record's index is looked up and the associated data is displayed on the right.
In this way, the functionality is very uni-directional, except for one thing: If the user changes the text in the Description textbox then the associated node in the treeview must also be updated.
Initially I've implemented just one AJAX Update Panel, surrounding everything. But my client has reported that on their slower network, he can see IE6 repopulating hundreds of items in the tree everytime an item on the right side is altered. So this got me thinking that perhaps I should add a second Update Panel encompassing all of the controls on the right.
If you were building such a form and wanted to minimize network traffic, where would you add Update Panels?
Robert W.
http://mwtech.com/downloads/public/StockMuckEditor_Capture.JPG
The treeview on the left is used to navigate down to a specific record. Once a bottommost node is reached the record's index is looked up and the associated data is displayed on the right.
In this way, the functionality is very uni-directional, except for one thing: If the user changes the text in the Description textbox then the associated node in the treeview must also be updated.
Initially I've implemented just one AJAX Update Panel, surrounding everything. But my client has reported that on their slower network, he can see IE6 repopulating hundreds of items in the tree everytime an item on the right side is altered. So this got me thinking that perhaps I should add a second Update Panel encompassing all of the controls on the right.
If you were building such a form and wanted to minimize network traffic, where would you add Update Panels?
Robert W.