Mon 30 Mar 2015 06:27:10 PM UTC, original submission:
I observed small differences in behaviour or syntax between Octave and MATLAB regarding figure/uicontrol - they sometimes correspond to undocumented features so I understand if they were not implemented in Octave but I thought some of them might still be relevant. Let me know if I should write several bug reports instead or wait for 4.0 release before doing so.
- Octave does not return all the handles of the default menu from a new figure:
i.e. Octave returns the handle of the figure only, while MATLAB returns the handles of the figure, menu and toolbar items.
- Difference between gco and gcbo:
at each click on the button, MATLAB displays the handle of the pushbutton for both gco and gcbo while Octave returns [] and the handle of the pushbutton, unless you click in the figure and then gco is the handle of the figure.
- Numerical content of the 'String' property of a uicontrol:
Octave returns an error as it expects a string while MATLAB will automatically convert to a string (with a call to num2str I presume).
- Interpretation of '&' in the 'String' property of a uicontrol:
In Octave, it creates an underlines B (as it would do for a uimenu, and enables Alt-B) while on MATLAB, it displays 'A&B'.
- Options for figure/uicontrol/... can be provided as property/value pairs and/or a structure:
MATLAB is fine with both syntaxes (I could not find it mentioned in the documentation though) while Octave only acceps the first one.
|