[Octave-bug-tracker] [bug #59242] ind2rgb/ind2gray errors with uint input containing the maximum integer value outside of colormap range

[Rik]

Follow-up Comment #6, bug #59242 (project octave):

Just so we stay Matlab compatible, ind2gray should clip the input based on the
number of colors in the colormap.  The documentation is:


If you specify X as an array of integer data type, then the value 0
corresponds to the first color in the colormap map. For a colormap containing
c colors, values of image X are clipped to the range [0, c-1].

If you specify X as an array of data type single or double, then the value 1
corresponds to the first color in the colormap. For a colormap containing c
colors, values of image X are clipped to the range [1, c].


At least in Matlab, only single, double, uint8, or uint16 inputs are
documented as allowed.  But, uint32 and uint64 *do* seem to work.  I wouldn't
get too caught up in trying to get this to work for strange combinations like
uint64 with more than flintmax entries.

    _______________________________________________________

Reply to this item at:

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

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