The Control class offers a ContextMenuStrip so that you can assign a menu to
be automatically displayed when the control is right-clicked. That's nice.
Why then don't the more complex controls provide you with an easy way of
determining WHAT was clicked?

For example, I have a tree view. I want to go the easy route and assign a
ContextMenuStrip to it. Then, in the Click event of the ToolStripMenuItem,
there should be an EASY way of determining what brought the menu up in the
first place! For example, I should be able to determine if it was the tree
itself that was clicked or one of the nodes, and, if a node, WHICH node. Am
I missing a property somewhere or do I have to pull tricks (generally
involving MouseDown/Up) to figure out "where I am"?

"Jeff Johnson" wrote:
Actually, they do. See `TreeView.HitTest' and
`TreeView.GetNodeAt' methods.

HTH
Alex

"Alex Blekhman" <tkfx.REMOVE (AT) yahoo (DOT) com> wrote


No, that's not what I call easy; that's the code I'm expecting to have to
write. I think the tree view control should provide ContextMenuTarget and
ContextMenuTargetType properties which I can just reference directly from
the Click event of the menu item.

"Jeff Johnson" wrote:
But what if you need to display different context menus for
different tree nodes? Also, don't forget that WinForms
controls are rather thin wrappers on top of Win32 common
controls. So, they expose whatever underlying native control
delivers. Sometimes even less (see my rants in
"Icon.FromHandle + ImageList = decreased color depth"
thread, for example).

Alex