When Cube is started, it can take a lot of time before all the shapes are correctly shown in Visual Overview. By default, there are around 10 tabs (views) loaded when the client is started. These contain a Visio file with a lot of shapes/tabs. It can take a lot of time before all shapes show the correct information.
How is lazy loading supported for Visual Overview?
Will it first load the tab that is open in your client?
When you use VdxPage to show different tabs with a '|' separated list, will it also perform lazy loading or will the subscriptions be closed when another tab is selected?
Is there a difference between using a variable instead of a '|' separated list for VdxPage?
RN 9613 describes that lazy loading is supported for children in containers (scrollbar), but is lazy loading also supported for Visio files loaded inside the child?
Good question Michiel. Lazy loading is a broad topic but Toon's answer is a great summary.
"Is there a difference between using a variable instead of a ‘|’ separated list for VdxPage?"
Yes, there is! Using a variable will make sure the previous page (including any subscriptions) is cleared before the new page is created.
Concatenating multiple pages with the pipe separator will perform lazy loading of the pages. That means the first page will be initialized and navigating to other pages will initialize them. These initialized pages will only be cleared when the Cube card is closed.