This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi there, I have a case where i'm providing my own IDiagramConnectionRelocator. As part of it's RelocateConnection() behaviour I will sometimes need to rebuild the entire graph from scratch rather than simply modifying the existing data. This triggers the existing nodes and connections to be removed, which (through a fairly deep callstack) eventually triggers a crash in FakeNode since it does not implement the Parent member. After racking my brains a little, I was thinking that the best solution might be to refactor the InboundConnectionPointRelocatorThumb_DragCompleted (and it's bretheren) to make sure that when the IDiagramConnectionRelocator was invoked that the temporary node and it's connection points were no longer referenced. ie: fix up the graph to the stable state it was in before the drag started, disposing the FakeNode and it's connectionpoint, *then* calling relocate. Simply fixing the FakeNode's Parent { get;} might also work, but I think the other solution is much more robust. Please feel free to ask if you need more details. -d |
|
|
Hello Drew I have made the change to the ConnectionRelocatorThumb as you mentioned here. This fix will be available through our next nightly build. Cheers |
|