[Octave-bug-tracker] [bug #48667] Colormap not controllable at the axes level

[Dan Sebald]

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

Here's the current documentation regarding a handle used in the colormap
function:


     If the first argument HAX is an axes handle, then the colormap for
     the parent figure of HAX is queried or set.


That is the way that Octave behaves.  But the change would be that colormap
now only applies to that axes.  (And one would think that, for example,
passing the color map into the imshow function would behave similar to calling
colormap(HAX, cmap) internally.)  The hidden property '__colormap__' approach
would work, but the colormap data should be visible in some way.  The handle
is passed into the function--is there a colormap object that shows up in the
axes children list?  That might be another way of doing it, but such a scheme
could end up with multiple colormaps attached to the axes, which doesn't make
sense.

    _______________________________________________________

Reply to this item at:

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

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