[Octave-bug-tracker] [bug #51082] Colormap should be tied to figure instead of axis

[Rik]

Update of bug #51082 (project octave):

                  Status:                    None => Duplicate              

    _______________________________________________________

Follow-up Comment #1:

This is complicated as Matlab has been changing the interface around colormap.
 It used to be that colormap was only a property of figure objects.  However,
in recent versions Matlab has extended colormaps to apply to axes objects as
well.  See http://www.mathworks.com/help/matlab/ref/colormap.html.

Octave currently only implements colormap objects for figure objects.  There
is a bug report to extend it to axes objects.  See bug #48667.

The reason why the code below works in Octave is that Octave searches for the
parent figure object of any axes and places the colormap data on the figure.


f=figure;
colormap(gca,'cool')
get(f,'colormap')


Thus, for Octave this will return the 'cool' colormap.  But for Matlab, the
'cool' colormap will have been placed in the axes colormap property.  While
the figure colormap property will still retain the default map.


    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/