Populate the XamDataTree with some nodes. Now disable the tree and then re-enable it. It appears that the virtualized nodes are totally messed up or confused. If anyone knows a work around for this, please let me know. Disabling controls and later re-enabling them is very common, especially in our business applications.
Thanks.
Hi,
A Service Release is about to be shipped, it contains a fix in that area, so if possible, please update your product with that SR and check if the issue disappears.
In the meantime, could you provide more information about your exact scenario or a sample code?
Are you using the Silverlight XamDataTree, are you doing anything else than just binding, disabling and enabling, etc.?
Thanks,
Thanks and this is good news to hear. How can I send you the sample solution that demonstrates this?
You can just paste your essential code in a post here, or you could use the upload file feature (Options -> Add / Update).
OK thanks. try this.
I used your sample and managed to reproduce an issue when disabling and after that enabling XamDataTree, however I am not sure what you mean by totally messed up or confused so, if you could clarify that would be helpful.
Anyway, as I mentioned earlier, there is a fix for the issue that I was able to reproduce in a SR which comes out today, so please update to that version and it should be gone.
Let us know if we you have any further issues or questions.
HTH,
Sure and sorry for the confusion. “Messed up and confused” is not very explicit, and since it was 3am, perhaps I was the one “Messed up and confused”. As you saw, it failed to enable correctly. I tried to reset it by setting the itemsource to null, and then resetting it back to a collection again. After doing this it looked a bit better and I was able to select one node, but other nodes seemed to be disabled and un-selectable, even though they appeared enabled. This behavior was very unpredictable and not what I would expect – hence the description “Messed up and confused”. Anyway, you saw the behavior and it sounds like it’s already being addressed. Thanks for the prompt responses!
HI,
This should be resolved in the latest Service Release.
Sincerely, Matt, Developer Suport Engineer