[Octave-bug-tracker] [bug #54610] imagesc doesn't implement ranges properly

[Pantxo Diribarne]

Follow-up Comment #1, bug #54610 (project octave):

Yes it is a bit odd case. The x and y arguments in image and imagesc functions
are supposed to be equivalent to setting the image object's "xdata" and
"ydata" respectively. The ML doc says

>> imagesc('XData',x,'YData',y,'CData',C) specifies the image location. This
syntax is the low-level version of imagesc(x,y,C). 

Now "xdata" and "ydata" are supposed to be two element vectors that indicate
the position of the *center* of the pixels at the corners of the image.

In the original example, setting a two element vector for a one pixel high
image makes no sense (there is only one center in the the y direction). It
would be interesting to know if Matlab produces an error or interprets the
[ymin ymax] as the coordinates of the boundaries (and puts the center at
(ymin+ymax)/2).

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?54610>

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