Thank you, it all works back to normal.

Thanks Pantxo, I confirm the warning has now disappeared.

I now notice an issue with 'text':

h = figure ();
u = uicontrol ("parent", h);
set (u, "style", "text", "string", "A")

get(u,"style") returns "text" but the widget still look and behave like a pushbutton.

I attached a new patch that makes style changes work as they did before cset 5535267e88ba, this is like Matlab: we store wrong values and warn about it.

(file #45884)

Actually the patch is not the right thing to do. The default "value" property should be handled by the graphics_object. What does Matlab do in those cases?

h = uicontrol ('style', 'popupmenu', 'string', 'A|B', 'value', 0)
% Is the object created? If so what does the following return?
get (h, 'value')

h = uicontrol ('style', 'popupmenu', 'string', 'A|B', 'value', 5)
% Is the object created? If so what does the following return?
get (h, 'value')

h = uicontrol ('style', 'popupmenu', 'string', 'A|B')
get (h, 'value')
set (h, 'value', 5)
get (h, 'value')

Now attached ...

(file #45864)

Adding Pantxo to the CC list.

The trouble seems to be that the default call to uicontrol creates a pushbutton object for which the "Value" property is 0 or 1 (and it is 0 in this case).

When the style of the uicontrol is changed to popupmenu the "Value" field is initially zero while the popumenu expects numbering to begin at 1.

Matlab handles this case without problem so we should too.