User`s guide

R2007b
16-6
New Function to Unwrap Sequences of Angles
The new unwrapMultipart function unwraps vectors of angles similarly to the
MATLAB function unwrap, except that it handles vectors that include NaN separators,
unwrapping each section separately. Use it to remove discontinuities from vectors of
longitudes, azimuths, or phase angles that contain NaN-delimited sequences and as a
replacement for the obsolete function smoothlong.
Improvements to Data Trimming in patchm and patchesm
The patchm and patchesm functions now completely trim away polygons and parts of
polygons that fall outside your current map limits. This improvement also affects fillm,
which calls patchm. Previously the patch functions simply shifted coordinates inward so
that vertices collected at the edge of the limits, where they would appear as lines along
map borders, unless obscured by the map frame. This change allows OpenGL to better
render the patch objects constructed by patchm and patchesm, making them more
compatible with the use of AlphaData to achieve transparency. See the release note
“Map Axes Now Display Transparent Objects More Easily” on page 16-8 for more
details.
Compatibility Considerations
The more complete trimming in patchm and patchesm means that there are
circumstances under which automatic reprojection can no longer display all the data
provided to these functions. Automatic reprojection causes map objects created with
plotm, linem, patchm, patchesm, and certain other display functions (but not
geoshow) to be removed, projected, and redisplayed whenever a call to setm changes
certain map axes properties, including the map limits and projection type. In the case
of patchm, a set of polygons will become unavailable for automatic reprojection if all of
the polygons are trimmed away completely. In the case of patchesm, which constructs
a separate object for each polygon, any polygon that is trimmed away completely will
be unavailable for reprojection, even if it would lie within newly defined map limits. In
either of these cases, you should delete the handle(s) returned by patchm or patchesm,
then repeat the original calls after changing your map axes properties.
Other potential compatibility issues:
• patchm and patchesm exhibit greater sensitivity to incomplete or incorrect polygon
topology.