Re: Colormap in meshc.m

[Henry F. Mollet]

Thanks. Works great now with one small potential problem remaining: I cannot
change the colormap of the contours once they have been drawn.
Henry
Details:
octave-2.9.14:1> [x,y,z]=peaks;
octave-2.9.14:2> meshc(x,y,z)
## Peaks and contours appear in colormap 'jet'
octave-2.9.14:3> colormap (gray)
## changes peaks plots to grey but does not affect contours
octave-2.9.14:4> colormap (jet)
## changes peaks plot to colormap (jet)

##New terminal
octave-2.9.14:1> colormap(gray)
octave-2.9.14:2> [x,y,z]=peaks;
octave-2.9.14:3> meshc(x,y,z)
## peaks and contours are using colormap 'gray'
octave-2.9.14:4> colormap (jet)
## peaks changes to colormap 'jet' but contours remain gray.



on 10/5/07 2:53 PM, Peter A. Gustafson at
address@hidden wrote:

> On Wednesday 03 October 2007 01:51:08 pm John W. Eaton wrote:
>> On  3-Oct-2007, gustafson wrote:
>> | Perhaps this is exactly what David meant... however can we trick gnuplot
>> | by sending a colormap that artificially spreads the desired colormap only
>> | over the mesh plot values and not the z-dz values, say by padding the low
>> | end of the colormap?
>> 
>> Before doing that, how about verifying that the gnuplot behavior is
>> intentional.  If it is, then OK.  Otherwise, fix the bug in gnuplot.
>> 
>> jwe
> 
> I found the bug... it isn't a gnuplot bug.  We should be specifying a
> colorband range in our surface plot stream.  The attached patch should fix
> the problem.
> 
> Pete Gustafson
> 
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://www.cae.wisc.edu/mailman/listinfo/help-octave