[Octave-bug-tracker] [bug #53217] Can't close window popping up after "gray" command while pager is active

[Dan Sebald]

Follow-up Comment #25, bug #53217 (project octave):

I like the individual color map flavors change.  It's too bad that initial
test of 'n' and whether there is an existing figure via the root has to be
repeated for every map.  Is there some way of doing code reuse by placing that
construct in just one of the color maps and calling that with a special
option?  Or somewhere else?

Yet, I still have questions about looking to the figure for the size of the
existing color map and using that to determine the size of, say, hsv().  The
reason is that Octave now has a figure color map and an axes color map.  How
can hsv() anticipate which one is of interest to the user?  Or across existing
and new figures, for that matter?

Could there be a difference in behavior of hsv() between these two?

colormap(hax1, hsv())

and

hsv()

Notice in colormap.m that the axes looks to be the color map source:


  [hax, varargin, nargin] = __plt_get_axis_arg__ ("colormap", varargin{:});


not the figure.

I do understand the "look-to-the-destination" approach, e.g., that if someone
sets their axes color map (as opposed to, say, "figure" or "global" color map)
to 256 levels.  That if s/he then just wants to change from one colormap
(GRAY) to another (HSV) but maintain the number of levels, it would be merely

colormap(hax1, hsv())

but somehow--knowing the way Octave syntax flows--I wonder if this gets too
confusing quickly based upon how many figures are open and what the current
figure/axes is.  Maybe it would be better to just tie the default N to groot
somehow.  No opinion, it's just a bit hazy to me as I currently perceive it.

    _______________________________________________________

Reply to this item at:

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

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