tan() Now Returns Correct Answers for Large Complex Variablestan() Now Returns Correct Answers for Large Complex VariablesThetanoperator used to returnNan+iNanfor large complex input liketan(1000i). Nowtan(1000i)returns the correct answer,i.
In MATLAB Verion 6.5, in an exported GUI, application data for an ActiveX
component was not available to the CreateFcn callback for
that component.
This problem has been fixed.
There is now an Editor/Debugger preference you can set to automatically remove autosave files when you close the source file. Select Preferences -> Editor/Debugger -> Autosave, and under Close options, select the Automatically delete autosave files check box. In the previous version your only option was to manually remove autosave files.
In Version 7.0, you can execute the callback routine for an edit text control by first typing the desired text and then doing one of the following:Prior to Version 7.0, clicking on the menu bar did not trigger execution of the callback.
- Click another component, the menu bar, or the background of the GUI.
- For a single line editable text box, press Enter
- For a multiline editable text box, press Ctl+Enter
In Release 13, the diff function could produce an incorrect result when passed a logical array. This has been fixed in this release.
Thevarfunction now accepts adimargument to allow the variance to betaken along any specified dimension.varalso now accepts N-D arrays.In addition, two minor bugs in the way
stdandvarhandle empty inputs have been fixed to make them compatible withsum,mean, and others.
- For an empty m-by-0 or 0-by-m input, where m > 1,
stdandvarnow return a 1-by-0 or 1-by-m empty, repectively, instead of a scalar NaN. Both functions still return a scalar NaN for an empty 0-by-0 input.- For an empty m-by-0 input, where
m > 1,std(x,0,2)andvar(x,0,2)now return an m-by-1 vector of NaNs, rather than zeros. For an empty 0-by-m input, wherem > 1,std(x,0,1)andvar(x,0,1)return a 1-by-m vector of NaNs, rather than zeros.
Converting a MATLAB 5.3 (R11) GUI to MATLAB 6.5 sometimes resulted in the error:Unhandled internal error in guidemfile. Reference to non-existent field 'blocking'This problem has been fixed.
In MATLAB Version 6.5, editing a GUI that contained auicontrolwhose Tag property was set to[](empty) sometimes generated the following error message:Unhandled internal error in guidefunc. Error using ==> set Value must be a stringThis problem has been fixed.
For any GUIDE GUI that uses a context menu, export from GUIDE sometimes failed with an error like this one:??? Error using ==> guidefunc Improper assignment with rectangular empty matrix.This problem has been fixed.
In MATLAB Version 6.5, some GUIs exported from GUIDE failed to open. In other cases, attempting to export a GUI resulted in one of the following errors:??? Error using ==> guidefunc Error using ==> == Matrix dimensions must agree. ??? Error using ==> guidefunc Error using ==> == Function '==' is not defined for values of class 'struct'.These problems have been fixed.
When saving a figure as a FIG-File, the full filename (including path) must be greater than 11 characters.
In MATLAB Version 7.0, the opening function, OpeningFcn, can
expect
the same set of figure property values when opening an exported GUI that
it would find when opening a GUI that had not been exported. This was not
always true in Version 6.5 and may have resulted in a variety of errors.
In previous releases, uicontrols with FontName 'FixedWidth' (or 'Courier New') and FontSize smaller than 12 were drawn with 12 point text. That has been fixed. The text is now drawn at the correct size.
For some Linux configurations, on MATLAB startup, several warnings of the form:
Font specified in font.properties not found ...
appeared in the Command Window because the JVM could not find required fonts. It did not affect MATLAB operations. The problem no longer occurs and you should not see the message.
The fwrite function can now save uint64 and int64 values.
Previously it worked only
on DEC Alpha; now it works on all supported MATLAB platforms.
In Version 6.5 of MATLAB, when you selected code in the Help browser documentation and demos, the entire line of code was selected. Now you can select just part of the line of code.
Theimfinfofunction now returns the correct image type for Version 5 truecolor Bitmap (BMP) images. Previously,imfinfohad erroneously returned the type 'indexed' for these images.
LU factorizations for full matrices now use a modified version of the LAPACK LU factorization routines and return more accurate results when encountering denormal pivots (i.e., smaller than
realmin). In previous versions, results may have includedNaNs; for example:A = [2^(-1050) 2^(-1050);0 0] [L,U] = lu(A) A = 1.0e-316 * 0.8289 0.8289 0 0 L = 1 0 NaN 1 U = 1.0e-316 * 0.8289 0.8289 0 NaNIn the current version, results are more accurate. For example, using
Aas above,[L,U] = lu(A) L = 1 0 0 1 U = 1.0e-316 * 0.8289 0.8289 0 0This improved accuracy carries with it a performance loss for any operations that use
luorlu-based\(backslash) for factorization of full matrices.
The imread function now imports certain 24-bit and 32-bit
truecolor
Windows Bitmap (BMP) images correctly. Previously, the images appeared to
be sheared.
The imread function can now import Windows Bitmap (BMP)
images that specify a negative value for image height. The BMP
specification uses negative values to indicate the image orientation. If
the height is positive, the image is a bottom-up image; if the height is
negative, the image is a top-down image.
Theimreadfunction now handles multisample TIFF images correctly. Previously, if the PhotometricInterpretation field was set to 'grayscale',imreadincorrectly assumed that the input image always has one sample per pixel.
MATLAB sometimes appeared to freeze when you ran an M-file that contained an
input function. The Command Window was actually hidden
behind another window, such as a Figure window, and you might not have been
aware that MATLAB was waiting for input. You had to bring the Command
Window forward and provide the input. The problem has been fixed. Now,
MATLAB automatically brings the Command Window foward for you to provide
input.
In version 6.5 on Macintosh platforms, MATLAB sometimes unexpectedly terminated when you accessed files via dialog boxes, such as File -> Open. This problem has been fixed.
On Macintosh platforms, press Command+., (that is the Command key and the period key) to stop M-file execution. This works when the key bindings preference is set to Emacs (MATLAB standard) or Macintosh. Ctrl+C and Ctrl+Break also stop execution on all platforms.
Using the Property Inspector from GUIDE sometimes caused MATLAB Version 6.5 to hang. This problem has been fixed.
The way that MATLAB loads MEX files on Windows has been revised so that it is now possible to put dependent DLL's in the same directory as the MEX file rather than having to put them in the application directory (/bin/win32). This permits users and third parties to distribute self contained collections of M, MEX, and DLL's without having to explicitly copy the dependent DLL's into a different directory.
In previous versions, you could not use a mouse wheel with MATLAB on some Linux platforms. The mouse wheel should now work with MATLAB on Linux, if your Linux system is configured to use a mouse wheel.
In deep directories on Windows (path length exceeding 150 chars or so), the Windows system command "move" fails with the message: ??? Error using ==> movefile The filename or extension is too long. This affects MATLAB's movefile command. The work-around is to use copyfile(fileName1,fileName2) delete(fileName1)
The multibandread function would sometimes allocate far more
memory than necessary when reading subsets of BSQ data sets. This bug is
now fixed. When you read a data subset, only the necessary memory is
allocated.
In MATLAB Version 6.5, running some existing GUIs from GUIDE generated the following error message:??? Error using ==> guidefunc Maximum recursion limit of 500 reached. Use set(0,'RecursionLimit',N) to change the limit. Be aware that exceeding your available stack space can crash MATLAB and/or your computer. Could not create figure: 127This problem has been fixed.
The regexp function supports up to 127 tokens. Additional
parenthesized expressions will not mark tokens.
The arbitrarily chosen number of 16 as a limit for tokens in the
regexp function has
been lifted, and now as many tokens as desired may be used.
In Release 13, for theregexpfunction, a token that matched zero characters was returned as [0 0]. This required special case handling, and also lost the information as to where in the string the token was.The new behavior is for the zero-length token to be denoted as [n n-1] where n is the number of characters into the string that the token matches nothing.
Theregexpfunction had a limitation that an expression could notcontain more than 256 characters. This has been fixed andregexpnow accepts expressions of any length.
For the regexp function, you could not embed string anchors
(^ and $)within an expression. You could use string anchors
explicitly only at the beginning and end of an expression, respectively.
This has been fixed, so that the anchors may be used anywhere within an
expression to assert the beginning or end of a string.
In Release 13, sorting a sparse row vector or sorting a sparse matrix along its rows, using the command sort(S,2), resulted in a segmentation violation. This has been fixed in this release.
In previous versions of MATLAB, integer values greater than 999,999,999 were printed in scientific notation. Complex integer values were printed in scientific notation even if they had smaller values. All uint8, uint16, uint32, uint64, int8, int16, int32, and int64 values are now printed showing all digits exactly regardless of their value or whether they are complex or not.
In Version 6.5, invoking the uiimport command with an output
argument caused MATLAB to print a warning and incorrectly return an empty
array. This was fixed in version 6.5.1.
In previous versions, copy and paste on UNIX did not always work reliably and as expected. For example, the pasted text was not necessarily the text you last selected with the middle mouse button, or the selected text was not pasted. Now, copy and paste operations operate correctly on UNIX platforms. There have been some changes in how copy paste works between MATLAB and a terminal window. If you experience any problems using the middle mouse button to copy and paste to a terminal window from MATLAB, try a different form of copying and pasting, for example, use the menu items.
Theverfunction ignores the case of arguments supplied to it. That is,ver signalandver Signalboth display version information for the Signal Processing Toolbox.
Video demos did not play in all platforms and browsers because of problems with Universal Naming Convention (UNC) paths. This problem has been fixed.