| Products & Services | Solutions | Academia | Support | User Community | Company |
| Download Product Updates | | | Get Pricing | | | Trial Software |
| Documentation → MATLAB |
| Contents | Index |
| Learn more about MATLAB |
New features and changes introduced in this version are:
GUIDE No Longer Copies Callbacks When You Duplicate Components
GUIDE M-File-Defined handles Structure Fields No Longer Become Permanent
In GUIDE, when you copy a component for which one or more of its callback properties are defined, the callback properties of the newly created component are now set to their default values, the ones you get when adding a component directly from the Component Palette. Previously, their values were copied from the corresponding callback properties of the original component. New callback subfunctions can be generated in the GUI M-file for the new component in the same way as for any component in the GUIDE layout.
If you have relied on the old behavior, in which the callbacks properties of the new component point to the callbacks of the original component, you will now have to explicitly change the callback properties, using the Property Inspector, to do that.
The handles structure that is provided to every GUIDE generated callback subfunction in the GUI M-file is constructed at runtime every time the GUI runs. When the GUI is fully initialized, the handles structure contains only handles to all the components in the GUI and custom data added in any CreatedFcn callbacks and/or the OpeningFcn. Previously, fields that the M-file had added to the handles structure could sometimes become a permanent part of the structure.
If your GUI runs well but displays error messages about missing fields in the handles structure when starting up, you may have to update the code in the GUI M-file where those fields are accessed. You may need to initialize those handles fields properly in a CreateFcn callback and/or in the OpeningFcn.
For UNIX platforms, the Location property of uigetfile and uiputfile is obsolete. Previously, for UNIX platforms only, you could use the Location property to specify the screen location at which the dialog box would originally be displayed.
Since the UNIX uigetfile and uiputfile Location property is now obsolete, MATLAB ignores any occurrences in existing code of the Location property
uigetfile(...,'Location',[X Y])
or the older use of X and Y arguments to specify location
uigetfile(...,X,Y)
A warning is displayed for either syntax, on all platforms.
The following functions are either obsolete or grandfathered in MATLAB 7.4 (R2007a): cshelp, figflag, getstatus, menulabel, popupstr,setstatus, hidegui, uigettoolbar.
The functions shown in the following table will continue to work but their use may generate a warning message. As soon as possible, replace any occurrences you may have of these functions with the function(s) shown in the following table, if any, or with other suitable code.
| Function | Replacement |
|---|---|
| cshelp, figflag, getstatus, menulabel, popupstr, setstatus | Grandfathered. There are no replacements. No enhancements will be made and only critical bugs will be fixed. No warnings will be displayed. These functions may become obsolete if replacements become available. |
| hidegui | Obsoleted. Now issues warnings. Set the figure HandleVisibility property instead. |
| uigettoolbar | Obsoleted. No warnings will be displayed until a replacement is available in a future release. |
![]() | Graphics and 3-D Visualization, MATLAB Version 7.4 (R2007a) | External Interfaces/API, MATLAB Version 7.4 (R2007a) | ![]() |

Includes the most popular MATLAB recorded presentations with Q&A sessions led by MATLAB experts.
| © 1984-2009- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |