The MindFusion Forums - Virtual Diagram that represent multi diagrams

(UTC)

The MindFusion Forums › Flow Diagramming Components › WPF › Virtual Diagram that represent multi diagrams

(Moderator: Slavcho)

‹ Previous Topic | Next Topic ›

Pages: 1

Virtual Diagram that represent multi diagrams (Read 2193 times)

solisgsandc YaBB Newbies Offline Posts: 40 Joined: Dec 18^th, 2009	Virtual Diagram that represent multi diagrams Jun 25^th, 2010 at 3:37pm	Print Post
	Is there a way to collect all physical diagram nodes, links, diagram items into a virtual diagram concept? I am investigating this strategy to divide the big diagram into manageable pieces. Is there also a diagram connector concept that connects all diagrams together.


	IP Logged

Stoyo God Member Offline MindFusion support Posts: 13230 Joined: Jul 20^th, 2005	Re: Virtual Diagram that represent multi diagrams Reply #1 - Jun 25^th, 2010 at 5:10pm	Print Post
	Do you mean splitting the data into several subsets displayed in different diagrams?


	IP Logged

solisgsandc YaBB Newbies Offline Posts: 40 Joined: Dec 18^th, 2009	Re: Virtual Diagram that represent multi diagrams Reply #2 - Jun 25^th, 2010 at 8:12pm	Print Post
	Yes. I am trying to come up with a way to deal with performance problems with thousands of controls in one diagram. Unless there is another idea such as making nodes invisible if not in viewing area. I am looking at the concept of diagram that is related to 1 or many adjacent diagrams. The relation is needed to know so that if I were to find a particular node that I am able to find this in adjacent diagrams. Also I could follow link connections to another diagram. I hope I am explaining myself clearly.


	IP Logged

Stoyo God Member Offline MindFusion support Posts: 13230 Joined: Jul 20^th, 2005	Re: Virtual Diagram that represent multi diagrams Reply #3 - Jun 28^th, 2010 at 8:03am	Print Post
	Quote: Unless there is another idea such as making nodes invisible if not in viewing area. This would be similar to ItemsControl virtualization, but the WPF built-in virtualization works only for lists. We'll see if we can implement a two-dimensional variant in a future release. Quote: The relation is needed to know so that if I were to find a particular node that I am able to find this in adjacent diagrams. Also I could follow link connections to another diagram. If you know how the big diagram should be divided into subsets, you can build a graph that represents the connections between these subsets, where a graph vertex represents a set in the original diagram. E.g. if node from set A is connected to node in set B, then you also have an edge connecting A and B in the representative graph. This would let you find related subsets quickly, and you can use "off-page connection" shapes as in Visio to represent the other ends of links whose node are in different sets. You could also run some layout algorithm on that representative graph to get the relative positions of different sets and so to determine where in the diagram to draw off-page connections in the currently display set.


	IP Logged

Pages: 1

‹ Previous Topic | Next Topic ›