octave @4.0.2: commands "uicontrol & uipanel" are not working - Mac mini o/s 10.11.5

[scaetd]

These commands issued in Octave 4.0.2 only produced blank white windows titled "Figure 1":

uicontrol('style','pushbutton','string','button')

uipanel('title','panel','backgroundcolor','r')

The first command should have produced a pushbutton graphic in the lower left corner of a new window. The second command should have produced the word "panel" inside a new red window.

Apparently all ui### functionality is broken which means that no custom GUIs can be run in this Octave 4.0.2 port.

[dan@…]

Just a confirmation that I have this problem, too. Just like the report, except that Octave is 4.0.3, running on a Mac Mini (late 2012) under 10.11.5. Would love to hear when this gets fixed. If whoever is working on it happens to be local to the SF Bay Area, lunch or coffee are available as a reward! Thanks.

[scaetd]

I recently upgraded MacPorts, Xcode, and upgraded to Octave 4.2 . The same problem was found. The uicontrol and uipanel commands for a custom gui still do not work! Can this problem be elevated in importance? It has been over 7 months since this problem was first identified. The developer of featool reports other users with similar frustration using his featool with Octave. He indicates that the problem appears to be... "the Mac port instead of using the usual Qt toolkit (irrespective of what Octave says) co-opt native Mac OS gui widgets to provide the same functionality. Unfortunately this does not include the uicontrol to custom guis won't show up or work. The only hope is that the Octave devs make a proper port, but alas that does not seem to be happening any time soon.

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

Replying to scaetd:

He indicates that the problem appears to be... "the Mac port instead of using the usual Qt toolkit (irrespective of what Octave says) co-opt native Mac OS gui widgets to provide the same functionality. Unfortunately this does not include the uicontrol to custom guis won't show up or work.

I can reproduce this problem, but I am afraid that I do not know how to begin to solve it.
I have ​reported the problem upstream.
Do you know the code that "co-opt[s] native Mac OS gui widgets"?

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

At some point between versions 4.2.0 and 4.4.1, this issue seems to have been fixed upstream.
Please feel free to reopen if it is still not working for you.