octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #61532] "Automatic limits for current axis" bu


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #61532] "Automatic limits for current axis" button doesn't respect "axis tight"
Date: Tue, 25 Jan 2022 16:22:31 -0500 (EST)

Follow-up Comment #20, bug #61532 (project octave):

I'll attach a "savefig" of the map I mentioned (a compressed an an
uncompressed one), to experiment with, plus a simple .m file to calculate the
min and max limits of all phenomena plotted in that map.

The explanation below of what I see happening is maybe a little complicated,
apologies, it's sometimes hard to exactly describe visual things esp. on a
non-native language.

What I see:
After zooming in along some rectangle (wide, or high) and then clicking the
"Automatic limits ..." button, the contents are made "tight" relative to just
one of the axis and the shape of the figure "rectangle" is retained. So the
"tight" property only works on one of the axes, where I had expected the
"tight" property to work on both axes.
Apparently the "tight" property of the axes is disabled by the zoom action and
isn't preserved, or fully preserved, by the "Automatic limits ..." button.
A manual "axis tight" before your patch restores the original tight axes.
A manual "axis tight" *with* your latest patch keeps the zoomed-in shape,
however.

Checking with Matlab r2022a prerelease, I see that the original shape of the
drawing is always retained even when zooming in into a very wide, or very
high, rectangle - Matlab apparently ensures that the largest zoom rectangle
dimension fits in the picture. Clicking the "Restore original view" button
restores the tight axes.

So Octave's behavior differs somewhat from that of Matlab, but TBH I don't
care :-) I just expect the "axis tight" setting to survive zooming in and out
and be restored by the "Automatic limits" button.

BTW Matlab refused to swallow the saved figure, complaining about compression
and/or other issues. Should I enter a bseparate bug report for that or is that
a known incampatibility?

(file #52730, file #52731, file #52732)
    _______________________________________________________

Additional Item Attachment:

File name: testmapc.fig                   Size:363 KB
    <https://file.savannah.gnu.org/file/testmapc.fig?file_id=52730>

File name: testmaplims.m                  Size:0 KB
    <https://file.savannah.gnu.org/file/testmaplims.m?file_id=52731>

File name: testmap.fig                    Size:1086 KB
    <https://file.savannah.gnu.org/file/testmap.fig?file_id=52732>



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61532>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]