|116849||Jun 18,2014 11:53 AM||Jun 27,2014 12:40 AM||ASP.NET MVC||9|
Sorry, need to qualify this - the check event fires for every checked item during the creation of the TreeView.
The TreeView "create" event doesn't appear to fire either: ...ClientSideEvents(e => e.Create("tvCreated")...Thanks,Rick
We regret for the inconvenience caused.
Query 1: is there way to prevent nodes from dropping "into" a child node? In other words I would like only a single level list and not necessarily a tree.
Query 2: Using IE I receive an error (“Error: Unable to get property 'nodeName' of undefined or null reference”)
Query 3: I have DropChild and DropSibling, yet I can drag and drop anywhere in the tree.
For query 1, yes we have option to prevent nodes from dropping into as a child node and we can achieve it by disabling the “dropChild” and “dropSibling” properties. But currently it is not working and we are facing issues with Drag and Drop options in treeview. The above reported issues are confirmed as a bug and we have logged defect reports for these issues.
Query: Is there any documentation that describes, for example, how to prevent dropping on a particular node?
Please find the API reference documentation for our JS components in the following link,
Currently, we do not have inbuilt options to prevent dropping from particular node. This can be achieved only as a workaround solution by preventing the drop event for the required nodes.
Query: I would expect the check event to fire ONLY after the creation of the TreeView AND the user checks a checkbox.
We have analyzed this query (“the check event fires for every checked item during the creation of the TreeView.”) and confirmed this as a bug and logged a defect report for this.
The Fix for all the above reported issues will be available in our next service pack release which is expected to be rolled out at the end of next month. We will update this thread once these issue are fixed.
Please let us know if you have further queries
Excellent, thanks for the update.
Thanks for the update. The fix
for the reported issues will be available in our next service pack release for
ASP.NET MVC. Our next service pack release is expected to be rolled out by the
end of next month (July). Once it is rolled out we will update this thread.
Please get back to us if you would require any further assistance.
This post will be permanently deleted. Are you sure you want to continue?
Sorry, An error occured while processing your request. Please try again later.