Equivalent to guidata in App Designer

I converted a GUIDE based applicatoin to App Designer. When I created a new variable in a callback, I would add it to handles. Then at the end of the callback I would issue a guidate command so that my new variable was accessible in other callbacks of the GUI. Example

handles.cpu_str = cpu_str;
guidata(myapp,handles)

The help tells me to not use guidata except with GUIDE and .fig. So how do I make these variables available? The help advised me to change my handles to app.handles, but this had no effect. I tried making a handles a public property. How should I do this

[William Day]

This is a pretty large app. It would be somewhat painful if I have to individually identify each variable that I what to share

[Walter Roberson]

Can you use the migration tool? https://www.mathworks.com/help/matlab/creating_guis/differences-between-app-designer-and-guide.html

[William Day]

Thanks Walter. I have figured it out. I did in fact use the migration tool. It creates a command like this at the start of all callbacks.

[hObject, eventdata, handles] = convertToGUIDECallbackArguments(app, event);

So my problem was the hObject in the command. I changed it as follows

[hObject, eventdata, app.handles] = convertToGUIDECallbackArguments(app, event);

and changed the guidedata command to and then it worked fine

guidata(hObject,app.handles]

I think that maybe the help should clarify that guidata can still be used in App Designer if it was migrated from GUIDE

Answer 1

[William Day]

Thanks Walter. I have figured it out. I did in fact use the migration tool. It creates a command like this at the start of all callbacks.

[hObject, eventdata, handles] = convertToGUIDECallbackArguments(app, event);

So my problem was the hObject in the command. I changed it as follows

[hObject, eventdata, app.handles] = convertToGUIDECallbackArguments(app, event);

and changed the guidedata command to and then it worked fine

guidata(hObject,app.handles]

I think that maybe the help should clarify that guidata can still be used in App Designer if it was migrated from GUIDE

[Jeffrey Topp]

I have a similar issue. I created an app in App Designer which has a button that calls a script. How do I access the data (equivalent to guidata) from inside my script? I'd rather not pass the status off all the checkboxes and what not into the script.

[Walter Roberson]

@Jeffrey Topp

You would have to make sure that all of the properties of the app are Public so that you can examine them off of app. from inside your script. If you want to prevent the script from changing the properties, you would need to mark the properties as not having write access.