Thank you very much for your help!
Kind regards,
Trison
It seems clear to me. There is another dependency source file/folder that you did not copy.
Bruno
rehash toolbox
-Spandan
"Bruno Luong" <b.l...@fogale.findmycountry> wrote in message
news:j1qguv$pnb$1...@newscl01ah.mathworks.com...
"trison " <fuda...@yahoo.com.cn> wrote in message
news:j1q9lv$673$1...@newscl01ah.mathworks.com...
It appears DECONVLUCY depends on some private helper functions that are only
accessible from within the Image Processing Toolbox directory. Therefore
copying it to another directory will not work.
Why are you trying to modify this function?
--
Steve Lord
sl...@mathworks.com
To contact Technical Support use the Contact Us link on
http://www.mathworks.com
-Spandan
"Spandan Tiwari" <span...@mathworks.com> wrote in message
news:j1r92a$3p7$1...@newscl01ah.mathworks.com...
I tried to catch the meaning of each code in deconvlucy, and to avoid any changes about it, so I copied it to a new M-file mydeconvlucy. Thank you very much for your advice. I learn a lot now.
"trison " <fuda...@yahoo.com.cn> wrote in message
news:j1ret2$ok7$1...@newscl01ah.mathworks.com...
*snip*
> I tried to catch the meaning of each code in deconvlucy, and to avoid any
> changes about it, so I copied it to a new M-file mydeconvlucy. Thank you
> very much for your advice. I learn a lot now.
If you want to read through DECONVLUCY to try to understand it without
risking accidentally changing it, just make it read-only. You can do this by
right-clicking on the file in Windows Explorer and opening the file's
Properties or using the FILEATTRIB function.
Or use a file viewing tool instead of an editor...
--
"dpb" <no...@non.net> wrote in message news:j1rgas$s1t$2...@speranza.aioe.org...
That works if you just want to read the code. If you want to step through
the code using the Debugger and examine the state at various points, which
is one technique I often use when attempting to decipher a piece of code,
you can do that without the Editor but it's much easier to do with it.
> That works if you just want to read the code. If you want to step
> through the code using the Debugger and examine the state at various
> points, which is one technique I often use when attempting to decipher a
> piece of code, you can do that without the Editor but it's much easier
> to do with it.
Good point...
--