Re: [Kmatplot-general] Documentation

[Laurent J. <lja...@fy...>]

On Thursday 16 May 2002 20:32, Hugo van der Merwe wrote:
> It's kmesh that I want to figure out. (One uses kaddaxes(1) to get 3D
> axes instead of 2D.)

Of course, I forgot that point.

Instead of killing kmatplot, a bad use of kmesh after kaddaxes(0) instead of 
kaddaxes(1) would have to return an error message.

>
> In my experience, kmatlot dies if one passes it e.g. kmesh(g), but is
> happy if you pass it kmesh(x,y,g). I have to replace meshgrid(1:256)
> with meshgrid(1:40) though, as anything larger causes the graph to not
> be displayed. With it displayed, it's a set of vertical planes, not a
> nice meshed surface...

Strange limitation. It's a bit annoying.

Kamil, it's a detail but, is the kaddaxes procedure is absolutely necessary 
in Octave ? 
I think that a good use for a kmatplot "octaved" will be to approach the 
matlab way where you have no equivalent of kaddaxes.

Another point, do you it is possible to control the colormap through octave ?
I think about something like 
	kcolormap("colormap_string");
But perhaps it already exists and I didn't have read correctly the doc (RTFM)?

Thanks,
Laurent.