Previously posted to wrong forum. I'm using Prometheus.
I implemented the load on demand demo. What I want to do is load the node from a web service call when it is expanded, and when it is collapsed I want to clear it (the tree can be very large, and I don't want to keep invisible nodes visible on the client side). Eventually, I'll implement a more elaborate caching mechanism, but here is the problem:
When I hook into the client-side NodeCollapsed notification and clear the node contents, the next time it is expanded my web service method is not called. Is there a flag or something I should be setting to let the node know it needs to re-populate again?
Thanks,
Joe
I implemented the load on demand demo. What I want to do is load the node from a web service call when it is expanded, and when it is collapsed I want to clear it (the tree can be very large, and I don't want to keep invisible nodes visible on the client side). Eventually, I'll implement a more elaborate caching mechanism, but here is the problem:
When I hook into the client-side NodeCollapsed notification and clear the node contents, the next time it is expanded my web service method is not called. Is there a flag or something I should be setting to let the node know it needs to re-populate again?
Thanks,
Joe
1 Answer, 1 is accepted
0
Joe
Top achievements
Rank 1
Rank 1
answered on 28 Mar 2008, 06:54 PM
Solved the problem. Something in the inner workings sets the expandMode property to 0 (should be 3) after the node is populated. Resetting it to 3 in the NodeCollapsed notification generates the behavior I am looking for.
Joe
Joe