Yeah, who knows ... it's probably something as simple as different development teams worked on the two different things and did things differently.


>Hmm, I'm not sure why the difference in accuracy for the DragEventArgs and the MouseEventArgs. It could be a bug but I would be guessing.
>
>>Thanks Cathi,
>>
>>That did the trick. I had been trying to get this to work a coupla weeks ago, and that was before I had known about the TreeView.GetNodeAt() method, which was probably the only piece of the puzzle that I was missing at the time. And, luckily, this is generic enough that I can probably put it in a TreeView baseclass and not have to worry about it again.
>>
>>But, I'm curious about one thing. It's interesting that the X,Y coordinates of MouseEventArgs is more accurate (if that's the correct description) than the X,Y coordinates of the DragEventArgs. In a similar type of operation with drag/drop (in fact, you may have been the one to post the code for me), I had to take the X,Y coordinates and convert that to a Point and use GetNodeAt(Point) instead of GetNodeAt(X,Y). I had thought it was an extraneous step when I originally was trying this drag/drop code, and so I tried using the X,Y directly, but it would never work. Any ideas why these behave differently? And how to know *when* to use X,Y and *when* you have to do the point conversion???
>>
>>TIA,
>>~~Bonnie