isoview(xmin, xmax, ymin, ymax) is poor and unhandy. Upgrade attached
@sgougeon)
Reported by Samuel GOUGEON (isoview_13974.zip (14.39 KB, application/zip)
isoview.sci + help pages (en, ja, pt)
BUG DESCRIPTION:
----------------
Presently, the only isoview(xmin, xmax, ymin, ymax) calling sequence
* acts only on the current axes: it can't be applied to another axes, to a set of axes, or to all axes of a figure, etc.
* does not allow to switch off the isometric status of an axes, or to commute its isometric status between on and off.
* demands reframing the axes with new bounds, even when only enabling isometric scales is wished.
This requires to priorly call gca() either to get existing bounds, or/and to enable isometric scales through .isoview attribute.
Calling the present isoview() therefore is useless and quite absurd.
* demands specifying all data bounds, even when some of them must be kept.
* does not allow to reframe zmin, zmax when the axes is in 3D.
A new isoview.sci implementation is attached. It removes all these limitations. The proposed new set of calling sequences is:
isoview
isoview on
isoview off
isoview(idAxes [,"on"|"off"])
isoview(idFigure [,"on"|"off"])
isoview(xmin, xmax, ymin, ymax [,zmin, zmax] [,"on"|"off"])
isoview(xmin, xmax, ymin, ymax [,zmin, zmax], idAxes [,"on"|"off"])
isoview(xmin, xmax, ymin, ymax [,zmin, zmax], idFigure [,"on"|"off"])
When the current axes is targeted, console oriented calls without () are very handy.
Updated help pages are also uploaded for en_US and existing translations.