Thu 08 Dec 2016 06:41:00 PM UTC, comment #4:
I can't get any of the following variations to crash except for the last one, which will always crash (eventually), although not on the first try to drag. If I drag slow it doesn't seem to crash, but quick movements seem to cause it. I crash it by panning the figure up out of the axis to the top of the screen in one fast motion (or after several tries). I tried all of these on Windows 10, but I first reported this bug based on Windows 7: so I can get it to crash every time on two different machines.
|
Mon 05 Dec 2016 10:16:19 PM UTC, comment #3:
Image pixels which are partially outside the axis are not drawn. See bug #49490.
Octave shouldn't crash though. Can you reproduce it with this simpler example?
|
Sat 03 Dec 2016 01:50:38 PM UTC, comment #2:
Confirmed with 4.3.0+ as well.
Release -> dev
Status -> confirmed
|
Fri 02 Dec 2016 10:36:38 PM UTC, comment #1:
On linux I have confirmed problems 1 and 2, but problem 3 does not occur, i.e., no crash. There is actually a 4th problem, which is what you wrote in the message: the image is appearing below the axis and not being cropped.
For comparison, the gnuplot graphics toolkit works in terms of image borders and pixel zoom. (Generally, panning doesn't seem to work in gnuplot, but it should be possible.) However, your first example fails when trying to overlay the box and points on the 2x2 center pixel block. So I have created another bug report for that: https://savannah.gnu.org/bugs/index.php?49757
|
Fri 02 Dec 2016 06:53:13 PM UTC, original submission:
I'm using GNU Octave, version 4.2.0, "x86_64-w64-mingw32".
I have several problems related to imshow(). First is that imshow() will not draw partial pixels when zooming or panning; second, under some conditions, the entire image doesn't show when the top of the image is not within the axis; third, I can reproducibly crash octave when panning/dragging the image up to the top of the screen.
Obviously the crash has the worst consequences, but problem 2 is what made me start the bug report. Trying to extract the bare-bones of the problem led to problem 1, which doesn't reproduce problem 2. I found problem 3 on accident while trying to create and test this bug report.
|