How to transfer data between apps using app designer

The simplest solution would be to couple the two apps. When you open app B send the object of app A to it. Then when app B updates x, it can update the property of app A.

A more robust solution would be to uncouple the two apps and add a mediator class. The mediator knows both app A and app B. It passes all the data between the two back and forth. Both apps don't need to know each other, only the mediator.

The reason I say this implementation is more robust is because tomorrow you may need app A to communicate with a third class instead of app B for some specific functionality. In that case you don't need to change app A, only the mediator class.

4 个评论
显示 2更早的评论隐藏 2更早的评论

TADA 2020-8-6

appMediatorExample.zip

I attached a zip file with a very simple example

you have a main app which has axes and a button to open a dialogue for adding new x-y values

The dialogue has two spinners and two buttons OK and Cancel.

If you click OK the value pair from the spinners will be added to the plot

This is implemented using callbacks rather than return values from any of the methods

the AppMediator class knows how to show a new "dialogue" window, and has a callback function for when that window is done

App2 accepts the mediator in the startupFcn and then when one of the buttons is clicked it calls the callback function of the mediator and sends the spinners values.

The mediator accepts a callback function when the showDialogue function is called and it then calls this callback function when the dialogue sends an "OK" callback;

App1 also accepts the mediator in its startupFcn and in turn when its "add" button is clicked will call the mediators showValueDialogue function, it sends a function handle as a callback to the mediator

The last trick is that the mediator also accepts a function handle to generate the dialogue window in its Ctor, so that none of the classes really need to be coupled.

If I wanted to go decoupled all the way, I would make the AppMediator class implement some interface and then I would make the apps know that interface rather than the AppMediator implementation so that true decoupling of all the classes can be achieved.

Then, the only one whoes coupled to anything is my main script - startAppMediatorExample which creates the main app (app1) and the mediator and tells the mediator to use app2 as a dialogue.

Hopefully this clarrified the general idea

Noah Griffiths 2021-7-27

Hi @TADA,

Wanted to thank you for this example and explanation as it promotes good coding practises. Global/properties sends shivers down my spine so when MATLAB's own documents recommends them I'm immedaitely searching for another solution. Thanks again!

TADA 2021-7-27

cheers Noah,

I know what you mean, globals give me an allergic reaction

请先登录，再进行评论。

Answer 2

sam0037 2016-6-23

1
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/290254-how-to-transfer-data-between-apps-using-app-designer#answer_226426

Hi,

You can use public properties as explained in the link below to share data between apps. And you can add a closeRequestFcn using the Callback button in the Editor tab of the APPDESIGNER window. Remember to add "delete(app)" in the closeRequestFcn or else the app wont close. I have attached a sample APP to illustrate the above. Run the SendData app which sends the data to RecvData app. Hope this helps.

http://www.mathworks.com/help/matlab/creating_guis/share-data-across-callbacks-in-app-designer.html#responsive_offcanvas

3 个评论
显示 1更早的评论隐藏 1更早的评论

Wouter 2017-4-5

Ho Nhu Y Nguyen did you already achieved this? I stubmle upon your topic now namely and am also wondering how to implement this behavior. Can you maybe share your findings if you have any?

Ho Nhu Y Nguyen 2017-4-25