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

[Markus Mützel]

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

The following is valid at least in Matlab R2016a. I don't know whether
something has changed in newer versions.

The axes do not have a "colormap" property directly. However, with the
function in [1], I found that there is a hidden "ColorSpace" property which in
turn has a "Colormap" property:

>> cs = get(hax, 'ColorSpace');
>> get(cs)
                ALim: [0 1]
            ALimMode: 'auto'
        ALimWithInfs: [0 1]
    ALimWithInfsMode: 'auto'
            Alphamap: [1x64 double]
                CLim: [0 1]
            CLimMode: 'auto'
        CLimWithInfs: [0 1]
    CLimWithInfsMode: 'auto'
            Children: [0x0 GraphicsPlaceholder]
            Colormap: [64x3 double]
    HandleVisibility: 'off'
              Parent: [1x1 CartesianDataSpace]
             Visible: 'on'


This is very HG2 which Octave doesn't support.


Rik's example in comment #12 results in two identical subplots (both using
colormap "winter"). However, I am still tempted to consider this a bug in
Matlab (at the very least it is not what a user would expect).

Could the patch provided in comment #11 be considered anyway, given that we do
not support HG2 (and probably won't in a long time).

[1]
http://undocumentedmatlab.com/blog/getundoc-get-undocumented-object-properties

    _______________________________________________________

Reply to this item at:

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

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