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
|
I'm evaluating your WPF diagram control for my application. What I need to be able to do is take a hierarchical object model containing 'nodes' with parent and child information and draw it as a top down decision tree. (On node at the top, branches equally spaced going downward.) I've spent a day playing around with the API which has raised a couple of questions on how I'd use your control.
Regards, Jon |
|
|
|
|
Hello Jon I would recommend using the standard Diagram type that we provide. This is a type of diagram that has no built-in validation rules making it easier to extend. You can see the standard Diagram type in action in the QuickStart sample. I suggest starting by implementing a custom type of node to suit your needs. The ActivityDiagrams sample will be the best place to look for examples of implementing custom nodes. You can extend the DiagramNode class and add connection points in the constructor. You could also create methods for adding more connection points dynamically based on the hierarchical object model. Take a look at ActivityDiagramStyle.xaml to see how to create and apply custom node styles. Let me know if you need any help with creating a custom node. Once you've got a custom node working, we'll work on positioning the connection points. -Jason |
|
|
|
