How can I get the pre-2014b behavior of hold on?

I often make 2-d plots showing a comparison of cases with a parameter 'On" of 'Off'. So I'll have several curves for the first case and then another set, using dashed lines, for the second case.

%The code would be pre 2014b
plot(x,y_on)
hold on
plot(x,y_off,'--')

How can I get the same result in 2014b?

Answer 1

[Jesse]

I use

set(gca, 'ColorOrderIndex', 1)

between calls to reset the color order, and give you the same behavior as pre-2014b

[Julius Kusuma]

The caveat is that this has to be called BEFORE "hold on". A bit annoying, MathWorks should change this.

[Mike Garrity]

I'm not clear on what you're referring to. I get exactly the same result if I do this:

rng(0)
figure
plot(randn(1,100))
set(gca,'ColorOrderIndex',1)
hold on
plot(randn(1,100))

or this:

rng(0)
figure
plot(randn(1,100))
hold on
set(gca,'ColorOrderIndex',1)
plot(randn(1,100))

Answer 2

[the cyclist]

Did the behavior of

hold on

change in 2014b? I didn't think so. I continue to use it normally.

What specific problem are you seeing? Can you plot a small, fully executable piece of code that results in something unexpected?

[Sean de Wolski]

It did change, hold on now continues using the next color on the axes' colororder.

[Julius Kusuma]

http://www.mathworks.com/help/matlab/graphics_transition/why-are-plot-lines-different-colors.html

[Mike Garrity]

The pre-14b behavior of "hold all" finally got promoted to "hold on".

Answer 3

[M J Schwartz]

You can edit hold.m (it is just an ascii mfile)

Add, 'ColorOrderIndex',1 in two places

 ...
    elseif(strcmp(opt_hold_state, 'on'))
        set(fig,'NextPlot','add');
        set(ax,'NextPlot','add', 'ColorOrderIndex',1); 
  ...        
    elseif(strcmp(opt_hold_state, 'on'))
        set(fig,'NextPlot','add');
        set(ax,'NextPlot','add', 'ColorOrderIndex',1);

save hold.m to a directory that is before all of matlab's stuff in your path. save as: ~/matlab/mymfiles/hold.m add to your startup.m path('~/matlab/mymfiles'], path)

Arrogant "improvement" of default behavior (in this case, matlab removed the default behavior of hold.m from even being an option!?) is a real PIA for someone with 20+ years of code. Don't get me started on perula, which lets us all see what it is like to be colorblind.

[Steven Lord]

With respect to the parula colormap, Steve Eddins did a four part blog series discussing why we made the colormap change. The feedback in the comments was generally positive. But there were some people who indicated they preferred or needed the jet colormap (the previous default) to which I responded:

"Note that the JET colormap is still included in MATLAB. You can change your figure or axes colormap to use JET using the COLORMAP function; you can even set it as the default figure or axes Colormap if you like.

http://www.mathworks.com/help/matlab/default-property-values.html "

You can put the command to change the default colormap in your startup.m file in your startup directory if you want to always use jet.

[David]

M J,

Agreed, the change in hold is rather foolish. Why not just leave well enough alone?