"inputdlg" was really handy for creating a dialog that would pause your code, get user inputs, and then continue executing based on those inputs.
Since there isn't a way to accomplish this workflow within the App Designer framework yet, I built this workaround to help me accomplish what I was looking for.
This utility allows you to accomplish 2 primary workflows:
1) call your dialog app from code and have it block MATLAB code execution until the user finishes with the dialog
2) call your dialog app from within another app (the calling app) and block user input on the calling app until the user finishes with the dialog
-- Allows you to take advantage of the great App Designer editing features
-- Allows you to build more customizable input dialogs compared to inputdlg
-- Will automatically return all public properties and editable values in UI controls
-- At its most basic level, it requires four (4) simple 1-line code changes to your App Designer app to enable this calling method
This code requires R2018a+.
Adam Sifounakis (2020). Creating pseudo-modal App Designer apps that return outputs (https://www.mathworks.com/matlabcentral/fileexchange/69411-creating-pseudo-modal-app-designer-apps-that-return-outputs), MATLAB Central File Exchange. Retrieved .
I specifically wanted to see if I can understand how 'double click' on list box items can work. Although it is a good example of a multiwindow app example, I could not understand the point of 'SettingsApp.mlapp' if you are not using it. If it is a customizable code that you want users to navigate and write down their own codes, they can easily drag down and create the same UI you provided in SettingsApp.