Why does MATLAB now open the property inspector for objects instead of run the openvar() function when the object is clicked on in the work space window?

Like the title says, in 2019a the default behavior is to use the openvar function which allows you to traverse through the properties as if the object were a structure, a very helpful behavior. In 2019b double clicking brings up the property inspector which isn't itself a deal breaker, but now instead of bringing along a dynamic link to properties of this object that also happen to be custom defined objects it shows them in an editable text field. There is no longer a dynmic link effectivly killing the data 'trail' and making debugging in 2019b all but impossible for my workflow.

Was this change intenetional or is it some bug introduced when they tryed to roll out the new property validation feature they implimented? I altready tried to strictly type my objects with this feature, something that in a loosly typed language would be a very bad expectation if it was necessary to get the property inspctor to work properly, but this did not do the trick.

If anyone knows if a fix is coming or if there is some workaround in the prefernces menu that can be used please let me know!

[catherine sandoval]

I have the same problem I think that it is a bug. It does not have sense to got to the property inspector. I can not work with datastores, only the link to Files works, it is no possible to review other properties.

Answer 1

[Henry Ip]

I know that at least 2019b Update 3 fixes this problem. In the Windows version, click on the Help downward triangle dropdown menu in the RESOURCES section of the MATLAB Toolstrip and find Check for Updates. You should be able to see an update to install. Good luck!

[Steven Lord]

I suspect this issue was captured as Bug Report 2043582. If it is, it is listed as fixed in release R2019b Update 2. Since updates for a given release are cumulative, installing Update 3 would also work.

Answer 2

[Kyle Owen]

I had the same issue and when I contacted MathWorks they said it's a known issue in 2019b that is being investigated, here's their response:

The current workaround is to use "openvar" as described below. More information on this function can be found in the documentation at at

https://www.mathworks.com/help/releases/R2019b/matlab/ref/openvar.html

In order to test this workaround, please execute the following in the MATLAB Command Window:

>> f = figure; % create a figure

>> openvar f % or "openvar('f')

Note that if you simply click on "f" in the variable editor, only the property inspector is opened. However, using "openvar" directly opens the variable and you can click to access sub-elements in the variable tree.

[Al in St. Louis]

It's a shame tab-completion doesn't work for openvar. Still it is better than no workaround.

[Nicholas Ayres]

I have mode my own function signatures for waaaay too many of MatLab's built in functions. -_-

Answer 3

[Steven Lord]

I recommend that you contact Technical Support using the telephone icon in the upper-right corner of this page and show them a small sample of your workflow that has changed. They should be able to determine if this change in behavior is a bug or is intentional, and can capture information about your use of the Workspace window and Property Inspector for the bug and/or enhancement databases as appropriate.

[Kurt]

Apparently this is still a bug in 2023b. The openvar workaround works.