Is there a way to save what you do in a toolbox as a script?

Hi All

PLEASE ONLY ANSWER , DO NOT COMMENT ; I AM BUSY AND NEED Notification

if I do not want to use directly a toolbox and want to know what are the scripts that make that toolbox run , I should record what I am doing on the toolbox , so there should be a way to save something like a macro , this is possible in some softwares like CATIA and Abaqus , is the same thing possible in MATLAB ?

[John D'Errico]

t is a good thing that none of us are busy like you. It must be nice to be so important.

It is time for you to learn how to use m-files, a fundamental concept of MATLAB. They allow you to write the scripts you so desire to build.

[farzad]

you've got me wrong , I did not get noticed when you commented , despite your comment had no use for me ,sorry but thanks anyway

Answer 1

[Image Analyst]

All the steps you do are recorded in the history panel. You can copy lines out of it and paste into a regular editor m-file window if you want to save it as a standalone m-file.

[farzad]

Thank you very much

[PeteNW]

I have a similar question, but it relates to a 3rd party toolbox gui. I'm running FracLab and I want to run a few of the functions implemented therein within a separate script. There is no track record left in the History panel. There are over 200 functions contained in the parent directory for FracLab so manually tracking depencies seems like a daunting task. Is there a simple way to programmatically record the function callbacks to make a macro even though the GUI callback history isn't recorded?

Thanks for your help!

[Image Analyst]

You could open a text file and then use fprintf() to write a line into it every time you call a function:

fprintf(fileID, 'Now calling fubar() at %s\n', datestr(now));
results = fubar(); % Call the function.

[PeteNW]

Thanks for the quick response! Are you suggesting that I put these statements into the beginning of each of the functions in the GUI's directory? To be clear, I'm not sure exactly which functions are being called by the particular operations I'm performing with the toolbox.

So are you suggesting that I use this to launch the toolbox within a function?

I apologize for the confusion, but I want to ensure that I understand your advice fully.

Thank you!

[Image Analyst]

No. What I'm suggesting is that in your code, you must know what functions from the toolbox you called. After all, at some point in time, you typed in those lines of code, right?

So just add another line of code, in your code, before you call that function, that logs the fact that you called it to some text file with a name you choose.

[PeteNW]

Ah I think I can clarify. First off, I really appreciate your help with this! I do not call functions from the toolbox directly. I have simply been interacting with the gui that the 3rd party toolbox presents. The buttons and controls in the gui certianly call functions but at no point do I actually write any function calls manually, nor does the gui leave a record in the history pane.

That's where my confusion is coming from; I am working with a 3rd party toolbox in Matlab, and though the outputs of the functions are visible within the active Matlab Workspace pane, no function calls are listed in the history. To implement a macro, I would either need to somehow make the function callbacks visible and thus trackable, or I would need to find the handle for the gui panel that I'm working in. Attempting to get a reference to the active gui pane, I have tried the 'gcf' placeholder, but it fails to see the open gui panels.

I apologize for not explaining this issue more clearly at the onset.

Thank you again for your time!

[Image Analyst]

Well to do what I said, you'd need to have the source code, and know what the function names were. If you have, basically a black box, then I don't think there is a way to log what functions are called, unless possibly you can run one of the reports that determine coverage. Click the little down arrow on the title bar of the Current Folder panel and see what reports you can generate.

[PeteNW]

Okay, I'll try this. Thanks!