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, We're evaluating flow diagrams in a scenario where we already have an existing dot-based layout engine to integrate.
The node positions have integrated fine, I simply set the Bounds property of a FlowDiagramNode. Is there a recommended practice for integrating the edge data? I've tried various approaches without success - such as constructing a FlowDiagramConnection with segment data directly (segment data doesn't seem to survive to our custom path converter), or using a custom Pathfinder to copy in our segment data (seems to be some sort of co-ordinate system transform going on).
Any suggestions greatly appreciated! |
|
|
Hello Here you will want to go with the custom Pathfinder approach. Implement the IPathfinder interface and the CreatePath method to return a list of Point objects based on the data you have. You will need to give the pathfinder to the diagram formatter. This can be done with the DiagramSurface.Formatter.Pathfinder property. Pathfinders are constantly used whenever the user moves a node. If your pathfinder is not going to be suitable for dynamic path updating, then you may want to try this: Try this out and let me know if it doesn't work for you or if you've already tried all this. Regards |
|
|
Hi Jason, A fresh pair of eyes on the problem this morning has found the errant scaling factor that was slipping into our connection data - the IPathfinder approach is working fine now :) (users moving nodes about is a bit awkward for the layout engine, but we'll work something out!) Thanks, -Matt |
|