Frederic Moisy

To Nick:

Yes, the problem is fixed since July 2010.
See the function "remove_efmenu_fig.m".

-- The author

Oooooooh... I must admit that Bjorn Gustavsson is totally right. This submission actually mimick to behavior of pcolor. Thank you for your remark, and sorry for this false good idea...
F.

Dear Basim Kakakhel,
Please try the following: ezfit(c,y,'y(c)=a*(1-exp(-b*c)')

Secondly, imagine this scenario:

You have a volume of images, and you want to scroll through those images, viewing each one. If they were monotonically spaced, you could just call h=image(X,Y,C(:,:,1)) on the first slice, then call set(h,'CData',C(:,:,i)) on the rest of the slices.

When they are NOT monotonically spaced, you now need to call h=uimage(X,Y,C(:,:,1)). The problem here is that the 'CData' has a new number of rows/columns, so for subsequent images you can't just update 'CData' like you could before.

Instead, consider if uimage also gave the *indices* it used to resample C monotonically. Now on the first image you could call:
[h,Xinds,Yinds]=uimage(X,Y,C(:,:,1))
and on subsequent calls you could now use:
set(h,'CData',C(Yinds,Xinds,i))

This would save re-calculating the resampling locations for each separate slice (since they are all the same), and it would also save deleting and re-creating image handles for each slice you want to show.

Frederic, I've just sent you an overhaul of your code that does just this (and includes the speed-up from my above comment).

Oh, just one question. Maybe it's just me, but I can figure out a way to use constants in an Ezfit FUN expression. Sure, I could use subs to replace known variables by their numerical values before using ezfit, but it would be very handy, in particular for scripting, if you could tell ezfit which variables *not* to consider unknown but rather use the currently assigned value for...