[Octave-bug-tracker] [bug #48272] unable to set a colormap named list by name

[Carnë Draug]

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

> Is your plan to remove all of the extensions (incl. (un)register), or just
the "list" option? 

All. Because there's no point in registering if there's no use for the
registry.

> In principle the "list" option is fairly useful on its own as it is an easy
way to find out available colormaps. Does the manual contain an overview like
e.g. in the on-line Matlab docs? I suppose there is.
> (I don't know the manual by heart, I just googled through the on-line manual
but haven't found an overview there).

In principle is it useful, but in practice is unused. And yes, there's a
section in the manual that includes a list of all colormaps. If you run "doc
colormap", it is followed by rgbplot (a function that maps a colormap), and
then by all the core colormaps.

> Speaking for myself, limitations are rarely a problem as long as they're
properly documented and don't provoke crashes or errors.

An example of an error is what happens with a colormap named list.

> GIS raster files read with the mapping package can have colormaps
("anonymous" ones until they are, well, "registered" as you call it); so I can
imagine the register / list features could be helpful when doing much work
with such files.

Do you have a real use case now where this is useful?

    _______________________________________________________

Reply to this item at:

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

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