Weird problem - hoping somebody can help. We recently migrated from 8.2 to 10.2. This started happening since then, was working before.
The drag and drop between 2 trees works ok, but within the same tree dragging from a top node and putting it down moves it one node down than expected.
Forgot to add the piece of code we are using to fetch the destination node.private
Point cursorPos = destinationTree.PointToClient(new Point(e.X, e.Y));UltraTreeNode destinationNode = destinationTree.GetNodeFromPoint(cursorPos);}
Hi,
What event are you using for this code?
Did you try examining the destination node to see if it's the correct node or not?
Are you using the latest service release?
How to get the latest service release - Infragistics Community
Any updates?
Like I said earlier, the drag drop works ok if we drag a below node on to a top node, but it goges one node down if we drag a top node on to a bottom node - within the same tree.
Our application is in production and is causing a lot of heart-aches now.
Pls help! Shd I create a case?
Hi
We also installed the latest service release, but the bug is still there :(
Any suggestions what can be done.
Hi Brian, Mike,
We downloaded the latest service release today and tried, but the issue is still there.
It will be very difficult for us to send the whole project. But I have attached 2 files which is what we are doing.
In the file "TFwkTree.cs" there are 2 classes one for the draw filter and another for the tree (classnme: TFwkTree) This class handles the different events.
The second file is "ApEqTVControl.cs" which inherits from the TFwkTree and implements the other events. You may just want to look at the below event handlers in this file:
Hope to have a solution soon, as we are very near to hitting the panic button.
-Anish
You attached only the draw filter code. It is difficult to analyze this without a complete test project that demonstrates the problem. One thing to note is that there was a bug in the UltraTreeNode.Bounds property implementation (bug 37407), that was fixed in September 2010, that would not be in the 2010.2 volume release but is in the latest service release. It is possible that the bug that is causing you problems is fixed in the latest 10.2 service release.
Hi Mike, Pls find the code attached. This was taken from the DragDrop sample of Tree and over-ridden to suit our needs. We used a 'BeforeDragDrop' to check if drop can be allowed.
We are using the latest service release of 10.2. This is now becoming a major issue for us as the tree in the main feature in our project which was working perfect last year. This is being used in more than 12 countries in our company.
Any suggestions are welcome which would help us resolve this issue ASAP. Forgot to mention that the drag and drop works perfect if we move the nodes in the upward direction i.e. a lower node on an upper one.