From: Ali Al-Radaideh on
Thanks us, it works now

Ali
"us " <us(a)neurol.unizh.ch> wrote in message <hv1948$ek4$1(a)fred.mathworks.com>...
> ImageAnalyst <imageanalyst(a)mailinator.com> wrote in message <9b251876-32f2-4e65-88cd-37b66aece343(a)u26g2000yqu.googlegroups.com>...
> > On Jun 12, 7:40 pm, "us " <u...(a)neurol.unizh.ch> wrote:
> > > ImageAnalyst <imageanal...(a)mailinator.com> wrote in message <c31cad43-f0c4-4586-b24f-aeeaf3aa6...(a)f7g2000vbl.googlegroups.com>...
> > > > Call colormap AFTER you call imagesc.
> > >
> > > ???
> > > ia, this would NOT solve the OP's problem, though...
> > >
> > > us
> >
> > ---------------------------------------------------
> > You're right. I didn't notice that he had quotes around jet, and
> > removing the quotes fixes it. I was just thinking that when you call
> > imagesc (which I rarely do since I prefer imshow) that it applies some
> > default color map and that if you wanted a special/different one you'd
> > have to do it after your image was displayed. However it appears
> > (after testing) that if you assign the colormap before you have even
> > created/displayed the image axes, it seems to keep that colormap and
> > not use the default one. That seems a little counterintuitive to me
> > (that a colormap set before an object was even created should take
> > effect), but I guess that's the way it works.
>
> note that COLORMAP sets the map of the GCF or - if no fig exists - creates a fig and sets its map...
> hence, if you set the map, then create another fig, the latter will use the default color map...
> thus, i fully agree -and in fact- most CSSMers set the colormap after they created the fig...
>
> us