Hello Andrew,

Thank you for your update on this matter.

I was able to reproduce the behavior you are seeing with the sample project you have provided, but this appears to be more of a timing issue between the addition of the node and when the actual XamDataTreeNodeControl “presenter” of the node is created, and as such, I would recommend moving the code that is trying to put the node into edit mode or scroll the node into a Dispatcher.BeginInvoke action. This will delay the code enough to let the XamDataTreeNodeControl be created, measured, and arranged.

For example, you can modify the Add New Child button click to look like the following and this will avoid the issue you are seeing:

        private void AddNewChildNoteBtn_Click(object sender, RoutedEventArgs e)
        {
            SampleData newChild = vm.AddChildNode(vm.Data[30]);

            Dispatcher.BeginInvoke(new Action(() =>
            {
                var items = tree.GetNodesFromItems(new object[] { newChild }, true);
                tree.EnterEditMode(items[0]);
            }), System.Windows.Threading.DispatcherPriority.Background);
        }

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

Yep, that solved the problem! Thanks!