Posted
on Jan 27, 2012
(permalink)
I have a treeview with a number of nodes that contain various editing controls that are generated from templates. The problem is that the checkboxes are being treated like radio buttons as it will only allow one at a time to be checked. When I check one, it appears the tree automatically unchecks any others in the entire tree, firing the checkchanged handler for each in its template.
This only seems to be exhibited when a checkbox is clicked, I can generate the tree with multiple check boxes checked, but as soon as you check one I see this behavior.
All the checkboxes have unique ID's.
When I place several checkboxes on the same page with their own checkchanged handlers, but outside of the tree, they do not demonstrate this behavior amongst themselves. Although even checking one of these, the ones in the tree do.
I added some code to the checkchanged handlers in the templates and checked the __EVENTTARGET param and kicked it out of any that didn't match the ID of the sender. This kept the underlying data correct, but when the page regenerates all the other checkboxes are still unchecked. This would seem to imply that the tree is somehow forcing this on the controls when they're rendered.
If not I don't know where else this would be coming from. Any insight is appreciated though.