App Designer: UITable Cell Selection Callback does not show variables in debug workspace + GUIDE UIs called by .mlapp UITable methods do not show uitable content

<<

>>

I have come across the following (seemingly connected) issues while starting to integrate App Designer UIs in a system of interconnected UIs made in GUIDE:

• .mlapp UITable callbacks (CellSelection, CellEdited) do not show variables in debug workspace. Also true for any code called by these callbacks
• GUIDE UIs using uiwait loose all uitable (display?) funcionality when called from the .mlapp's UITable callbacks

I've made the two simple example GUIs attached to demonstrate:

• app1.mlapp is the starting point - please open and set a breakpoint in both the "ButtonPushed" and the "UITableCellSelection" methods (no matter where)
• start it and click the "button", invoking the "ButtonPushed" method
• close the example GUIDE UI again - it has no other functionality than filling its table with "foo" and "bar".
• everything was as expected: One can see expected variables in the method's debug workspace. The GUIDE UI that is called works just fine, as well as the called some_function.m. They also do show their debug workspace correctly when you set breakoints in these.

so far, so good.

• however, now select a cell in the table, invoking the CellSelection Callback
• Issues:

1. the workspace of the method is displayed empty when hitting the breakpoint. this seems to be true for any code called by the UITable's methods (as can be demonstrated by setting a breakpoint inside the guide_ui or "some_function.m" supplied in the example)
2. additionally, the table in the GUIDE UI does not display its elements.
3. both is true for any chain of code that has initially been called by a .mlapp UITable method.

I guess I have to flush/refresh something, as the UITable's Callback seems to block some general MATLAB UI functionality. I tried the usual suspects (refresh etc.) but without success.

I would be very glad on any feedback.

Further info:

• all above also true for CellEditCallbacks (not shown in example)
• GUIDE UIs not using uiwait do not loose their table functionality when being called form a .mlapp's UITable's callbacks. Also, .mlapps called by UITable's callbacks do not seem to be affected.
• other GUIDE UI elements (e.g. text field etc.) do not seem to be affected.
• they still all suffer from not showing debug workspace content which is VERY sad
• had to zip the files - mlapp is not supported. This also is somewhat... not so cool ;)

[Adam]

Is the workspace actually empty in the CellSelection callback or is it just not showing up in the workspace UI? e.g. if you type

app

on the command line in your breakpoint does it exist? Sometimes the workspace UI is sluggish to update and needs an F5 to do so or just fails to show variables, but they still show up when accessed from command line.

[Dominik Schuster]

Thanks for your reply.

Yes, - I forgot to mention: Everything in the command window works as expected.

I get the

 K>>

can access "app" and "event" as expected.

F5 and all kinds of refresh/drawnow/uiresume() etc. do not change anything, unfortunately.

To me it seems that during execution of the UItable callbacks in .mlapps, some general MATLAB UI functionality is on halt somehow. All code does it's job. Workspace explorer and GUIDE (with uiwait) uitables do not show anything, however.

Have you been able to replicate the behavior using my example file or otherwise?

[Adam]

I haven't been able to try at the moment. I'm in the middle of a task with 25 files open in my editor so don't want to be throwing something completely unrelated into the mix currently!

[Dominik Schuster]

Have reply from MathWorks tech support - known bug, no patch or workaround at the moment. Thank you anyways Adam!

[Spencer Laddy-Locks]

@Dominik Schuster I must thank you,

You prevented me from ripping some hair out (it was a close one, trust me). It's still not fixed in 2019a. @Adam Is there a way to get attention to this at all, or is it a lost cause at this point?