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

[Niklas Wahl]

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

Ah, yes, 64-bit integers are valid input, so your patch is much more robust
than my quick&dirty solution. I just checked it out and it looks good to me. 

Regarding the current implementation: I'm not really familiar with octave
development yet and how ind2x came to be. Currently, when using small
datatypes like uint8, the expansion of the map can be more efficient (small
colormap vs large image)? But as you stated the problem comes with larger
datatypes (uint32,uint64), where the map could become too large for indexing
depending on the values in the image.

    _______________________________________________________

Reply to this item at:

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

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