Hi Mike.

I am only concerned about the vertical scrollbar.

I have a small application with a hierarchy of physical locations. When the user doubleclicks on an item, a new window opens where he can edit the properties of the location. Recently a user complained that the window opened when he tried to scroll through the list. He simply clicked the "up" arrow a lot of times very quickly.
The control thinks it is a double-click.

Unfortunately there is no NodeDoubleClick event, so I think I have to do as you say and use the UIElements.

Thank you,
Jørn

this code works for the most part.  doesn't take into consideration the expansion indicators.  if a node is selected, then you double click an expansion indicator, node will not be null, and my double-click event code will run...

I tried this as an alternative, and did the same thing:

UltraTreeNode aNode = this.HierarchyDataSetTree.GetNodeFromPoint(new Point(margs.X, margs.Y));

Yes, they are. You could do something like this if you want to "filter out" hits on the expansion indicator:

void treeControl_MouseDown(object sender, MouseEventArgs e)
{
    UltraTree treeControl = sender as UltraTree;
    UIElement controlElement = treeControl.UIElement;
    UIElement elementAtPoint = controlElement != null ? controlElement.ElementFromPoint( e.Location ) : null;
    NodeSelectableAreaUIElement nodeElement = null;

    while ( elementAtPoint != null )
    {
        nodeElement = elementAtPoint as NodeSelectableAreaUIElement;
        if ( nodeElement != null )
            break;

        elementAtPoint = elementAtPoint.Parent;
    }

    if ( nodeElement != null )
    {
        UltraTreeNode node = nodeElement.Node;
    }
}

I don't want to filter out hits on the expansion indicators, I just don't want double-clicking the expansion indicators to qualify the same as double-clicking the node text or node image. 

For example:  Right now, if a node is selected, and the user clicks any expansion indicator twice, quickly, the double-click event fires and my code runs as if they clicked a node.  This is very confusing for a user.

Can we please get a NodeDoubleClick event?  Seems logical to me that double-clicking a node is going to be the most common UI action for a treeview control...

Thanks for the code samples. I was able to use them to quickly solve most of my current problem, but there's still an issue.

To summarize, I have a tree in grid mode with two bands. The root band forbids selection. Double-clicks expand or collapse a node. The child band allows selection (extended across multiple parents). I want to reserve double-clicking for entering edit mode.

Using the above code, I recognize when to enter edit mode when double-clicking a selected row. It almost always works. 

My problem is that, only in the very first child band, if a row isn't already selected, double-clicking it doesn't raise the double-click event, so that I have to double-click again. I experimented with different click speeds, and there's no question that the double-click should be happening but isn't. All other child bands register the first double-click for as-yet-unselected rows.

Any ideas?

I don't have a concise repro scenario to upload at the moment.

Yes, I checked that the event wasn't being fired.

I am handling the AfterSelect event to start a potentially lengthy operation. I thought maybe the double-click timing was getting disturbed with so much time spent on the first click, so I put the time-consuming parts into a timer tick event handler. That fixed most of the problem, which looks increasingly application-specific, so consider it resolved. I'll post again if I run out of ideas.

Thanks for responding so quickly.

The DoubleClick (and MouseDoubleClick) event is raised by the System.Windows.Forms.Control class, so I have no explanation for why the event would not be raised when the cursor is positioned over certain nodes. I assume you put a breakpoint at the entry point of the event handler and confirmed that the event itself is not firing. If possible, please attach the test project so we can take a look.

I was sloppy in referring to child bands, so here it is again.

Only in the child rows of the first row of the root band, a double-click on an unselected row doesn't raise a double-click event. In child rows of subsequent rows of the root band, the event is fired as expected.