[Feature Request] - Add property to Tab Container to save state of embedded views

[laura.strydom]

Good day,

I want to submit a feature request to add a property to the Tab Container that will allow to save the state of embedded views when switching between tabs.

Currently, the Tabs property has an internal property called runWhileHidden, and it determines if contents of the tab loads once the tab is first activated, and if it should persist while in the background when the currentTabIndex changes.

While this works, when another view is embedded on a tab, any changes made on the embedded view doesn't persist when switching between tabs.
A current workaround is to pass the data back up to the embedded view binding by changing all bindings for passing the data down to bidirectional. This is not great, especially if you have to do it for a lot of parameter bindings just for 1 view; and then your tab container has multiple embedded views

It will definitely make life easier if another property can be added that allows child components to stay persistent upon tab changes.

Thanks!

[jlandwerlen]

You should post here as well.

Inductive Automation Feedback

[pascal.fragnoud]

@laura.strydom

While this works, when another view is embedded on a tab, any changes made on the embedded view doesn't persist when switching between tabs.

Really ? It seems to work for me. Can you give more details on what doesn't work ?

[laura.strydom]

So in our testing, the embedded view on the first tab is a custom table made out of a flex repeater. It has a column for parameter names and a second column for the value of each. When the view is opened, the default values get pulled through for the parameters.

If you click on a parameter value, it allows you to change it (changed it from Null to Tanker 1.

If you click on another tab, and then navigate back to the first, the values all change back to default.

This happens even if we have runWhileHidden enabled on all tabs.

A short video would've demonstrated it better, but I hope the screenshots explain it somewhat.

[Hayden_Watson]

Would it be possible to create an object in your custom session properties and bind them to there. They should then persist for that entire session.