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

Hi Joesn,

     In that case, you are probably using the ActiveNode to get the node that was double-clicked. But that's not really a good idea, since the user could double-click on empty space in the tree or on an expansion indicator and you probably don't want to trigger at this point. 

    What I would do in DoubleClick is something like this:

    UltraTreeNode node = this.ultraTree1.UIElement.LastElementEntered.GetContext(typeof(UltraTreeNode)) as UltraTreeNode;

    if (node != null)

        // Do something

    This way you only respond if the last element the mouse entered is inside a node.  

Yes, that did the trick!

I wasn't aware of the LastElementEntered property.

Thank you very much.
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));

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.

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?