[Octave-bug-tracker] [bug #36594] imshow error after changing colormap

[Pantxo Diribarne]

Follow-up Comment #3, bug #36594 (project octave):

Here is the result of the script slightly modified to show differences with
octave behavior:


im=uint8([0 1 2 0; 0 1 2 0; 0 1 2 0; 0 1 2 0]);
map=[0 0 0; 1 0 0; 0 1 0; 0 0 1; 1 1 0; 0 1 1 ; 1 0 1];
im_dbl = double (im) + 1;
colormap (map);

image ([], [], im_dbl);
xlim1 = xlim
axis ('equal');
xlim2 = xlim
ylim2 = ylim
axis ('tight');
xlim3 = xlim
axis ('image');
xlim4 = xlim
clf;
imshow (im_dbl, map);
xlim5 = xlim

## result
xlim1 =
    0.5000    4.5000

xlim2 =
   -0.0358    5.0358

ylim2 =
    0.5000    4.5000

xlim3 =
    0.5000    4.5000

xlim4 =
    0.5000    4.5000

xlim5 =
    0.5000    4.5000
 

Indeed, in ML, axes limits include the half width of the pixels on the
boundary when necessary. 

Equal mode is different in octave but maybe those tests about xy/lim should be
part of another bug report. AFAIU this bug is now mainly about octave openGL
not being able render unint8 images properly.


 

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message posté via/par Savannah
  http://savannah.gnu.org/