Best practice for saving and loading axes children from and to an app designer axes?
2 views (last 30 days)
Show older comments
Edited: Kristoffer Walker on 22 Feb 2023
I have an app created in app designer. It has 3 GUI windows. The master window declares a public data container, which is subsequently written to by two slave windows. Each slave window has several figure axes. On closing of a slave window, I would like to save the slave figure axes objects to the master data container such that when the slave window is opened again, I repopulate the slave window figure axes exactly as they were before. What would be convenient of course is something like this for save:
app.MasterCallingApp.Slave1Data.axes1 = app.UIAxes1;
and something like this for loading:
app.UIAxes1 = app.MasterCallingApp.Slave1Data.axes1;
What is the best practice for how to accomplish this? I did a bit of searching and landed on some leads, but I tried some of them without success, and others look too complicated for me to consider.
Thank you for your help!
Timo Dietz on 22 Feb 2023
Edited: Timo Dietz on 22 Feb 2023
I'm using setappdata/getappdata for things like this.
You can store/get arbitrary data (structs, objects, ...) e.g. to an app or figure, accessible via a name you can freely define.
Find more on Develop Apps Using App Designer in Help Center and File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!Start Hunting!