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?
The first part of your question is more of a core matter, meaning it doesn't really have to do with Visual Overview.
By default, any card that is loaded in DataMiner Cube will initialize its selected page, regardless of whether or not the tab is currently selected. That means if Visual Overview is your default selection, the first page of the Visio drawing will be loaded from the get-go.
Any tab within Visual Overview is lazy loaded. That means the tabs won't be loaded until they have been selected. This includes embedded tabs.
Once a tab is loaded, it will stay in memory (and thus keep its subscriptions) until the card is closed or the tab/page is otherwise removed (for instance when embedding a single page in a shape through a session variable and changing that variable).
As for the last part: yes, the entire child shape will be lazy loaded, which means any embedded page in it will get the same lazy loading.
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.