Hi All,

I am testing VirtualizationDiagram ('faster' repleacement for Diagram with a big number of nodes and links). We have two collections there: NodesSource (instead of Nodes) and LinsSource (instead of Links).

In our project we are using ContainerNode (as a nested diagram). Unfortunatelly ContainerDiagram has no 'brother' like: VirtualizationContainerDiagram and there is no NodesSource and LinksSource properties (only Nodes and Links).

What is a correct way of applying VirtualizationDiagram when such diagram contains ContainerNodes (with its own nodes and links)?

Thanks in advance for any advice.

Regards,
Z

Hi Slavcho,

Thank you for your answere.
I have prepared a 'formal' change request here:
http://mindfusion.eu/Forum/YaBB.pl?num=1494247571/0#0

Regards,
Z

Hi,

Thank you for the initial support of the virtualizaiton of multiple node types.

In our case ContainerNodes might be quite big, let say several ContainerNodes in the Diagram with hundreds (or even thousands) of nodes/links insde one ContainerNode. It means that ContainerNode can be much bigger than the visible diagram placeholder on the screen.

What we would expect is that 'nested nodes' (nodes inside the ContainerNode) should be 'virtualized' as well (should be realized/materialized during scrolling). It is not enough to load all nested nodes at once into ContainerNode when ContainerNode is realized.

Is such behavior possible/planned for the next release?

Best regards,
Z