Hi Andrew,

Thanks for the reply.

The thread that you pointed me to isn't terribly helpful because the NodeDraggingStart event doesn't appear to know at any point what the droptarget will be. What I really need is the ability to disable the droptarget dependent on the types for both the dragsource and the droptarget.

With that said, I was able to get something kind of working through the NodeDragDrop event. I look for the type on both the dragnode and the droptarget, then set 

e.DragDropEventArgs.OperationType = Infragistics.DragDrop.OperationType.DropNotAllowed;
e.Handled = true;

This seems to work, the only issue at this point is the styling of the cursor as it hovers over the droptarget. It indicates that a drop should be possible, but this logic disables it. Any clues on how I can restyle the template?

Thanks for the reply!

Unfortunately it doesn't seem to work when using hierarchical data. I can disable the schemas at the top and that appears to work, but it still allows a drop into the collection of the schema's children. And because I don't have any idea for how that structure will look or how deep it will go, I have to do it recursively.

I did find a way to do something similar in the DraggingStart event by setting the IsDropTarget property on the XamDataTreeNode. Again I have to go through the XamDataTreeNodesCollection recursively looking for the types, but doing it that way by setting IsDropTarget to false appears to work. Any thoughts on that approach?

Hello Tracie,

It is true that if you disable the parent “schema” node, but the child nodes are still enabled that since they are deriving from the same base class, it will still be possible to drag to them.

Regarding a recursive method to loop through all nodes in the XamDataTree though, I would recommend something like the following:

        public void RecursiveNodeCheckMethod(Type type, XamDataTreeNode parent)
        {
            System.Diagnostics.Debug.WriteLine(parent);

            if(parent.Data.GetType() == type)
            {
                // Type matches
            }
            else
            {
                // Type does not match
            }

            if (parent.HasChildren)
            {
                foreach(XamDataTreeNode node in parent.Nodes)
                {
                    RecursiveNodeCheckMethod(type, node);
                }
            }
        }

If you call into this using a simple loop through the top-level Nodes collection of the XamDataTree and call into it for each node, this will allow you to check all of the nodes and pass in the exact Type that you are looking for. The “parent.Data” above will return the underlying data item of each node, so you can check that against each node being looped through.

I hope this helps. Please let me know if you have any other questions or concerns on this matter.