GUI - empty property inspector

I have a problem, I don't know why the property inspector in GUI doesn't show anything, it's empty. I checked the other computer in my university lab and it was OK. and it's just my computer problem and can't solve it.

http://imageupload.co.uk/files/7opcser3lez43sdtyyel.png

[Subhrajit Rath]

I am getting the same issues on R2019b.

Answer 1

[Gaia Tavoni]

I have the same problem. I get the error:

Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at com.mathworks.page.plottool.propertyinspectormanager.PropertyInspectorManager$3.run(PropertyInspectorManager.java:203) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756) at java.awt.EventQueue.access$500(EventQueue.java:97) at java.awt.EventQueue$3.run(EventQueue.java:709) at java.awt.EventQueue$3.run(EventQueue.java:703) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80) at java.awt.EventQueue.dispatchEvent(EventQueue.java:726) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

How can I fix it?

Answer 2

[David Sanchez]

try the following:

h=plot([1 2],[3 4]);
inspect(h)

If your property inspector shows up properly, you have a problem with the GUI configuration. If it shows up empty, I think something did not install properly during the installation process.

[Ahmadreza]

thanks. again it's empty.

Answer 3

[Unai Vicente]

I have the same issue here, I tried in 2 different macs running catalina which, for version 2019b says its compatible. Had the same issue on the previous OS X and Matlab release, anyone running matlab on mac having the same problem?

[Stepan Lakibchuk]

Oh, God, yes, it is hard to understand, I tried to reinstall it, but result is still the same! Is it because of Catalina?

Answer 4

[Alireza Karimi Bidhendi]

I have the same problem. Mac OSX Catalina, R2019b Matlab version.

Answer 5

[Rolfe Power]

Same problem here on Fedora 31 with R2019b. When attempting to open the property inspector either through the gui or calling inspect on the plot handle, I get:

Exception in thread "AWT-EventQueue-0": java.lang.NullPointerException
	at com.mathworks.page.plottool.propertyinspectormanager.PropertyInspectorManager$2.run(PropertyInspectorManager.java:167)
	at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
	at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
	at java.awt.EventQueue.access$500(EventQueue.java:97)
	at java.awt.EventQueue$3.run(EventQueue.java:709)
	at java.awt.EventQueue$3.run(EventQueue.java:703)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:728)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:205)
	at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

Following this, any attempt to open a property inspector (even of a different plot) presents an empty window.

[yashvini shukla]

I have the same issue, was anyone able to solve this?

Answer 6

[Han HU]

I have solved this problem by disable the web proxy. Hope this will help others.

Answer 7

[guodong yao]

i have the same question after mac os updated to ventura. how to fix it