How to make available initialization variables in workspace
4 Ansichten (letzte 30 Tage)
Ältere Kommentare anzeigen
Hello,
when a script, after declaring variables, I create a loop (eg. while) they are available in the workspace at the end of the loop
Is there a way to make them available since the execution of the script?
2 Kommentare
Matt Kindig
am 27 Sep. 2012
I think I understand your question. You're wondering why the workspace variables are not displayed in the Workspace during the loop execution. The reason is that the Workspace is not refreshed until the script is finished completion. Refreshing the Workspace during script/function execution is a feature that I've also wished for!
Antworten (2)
Kevin Claytor
am 27 Sep. 2012
You probably want to set a debug point somewhere in the while loop - either use the debug command or click the tick mark next to the line number. The program will pause at that point and give access to all variables in the current workspace. Here's a video to get you started.
Image Analyst
am 27 Sep. 2012
If you have a script, the variables will remain in the base workspace:
File test.m:
a = 42;
b = 'These will hang around';
If you have a function, then will vanish when your m-file finishes:
File test.m:
function test()
a=42;
b = 'These will NOT hang around';
Note that the "function" line in the second file turns it from a script into a function, and that means that the variables are local to that function and will vanish when the function exits. If it's a script, like in the first case, the variables will still be there for you to inspect in the base workspace.
Understand?
11 Kommentare
Image Analyst
am 29 Sep. 2012
Bearbeitet: Image Analyst
am 29 Sep. 2012
The workspace should get updated every iteration. workspace simply shows the panel - it doesn't force the panel to update. You definitely don't need it inside your loop! If you're in a really intensive tight loop and you find that the workspace panel does not immediately show the changing values, you can try to put a "drawnow" in your loop to try to force the user interface to update, or else display the values in the command window or a GUI like I said earlier. If you use a custom GUI, and it's in a tight loop, then you're going to have to use "drawnow" in the loop to get the GUI to update on every iteration. Otherwise, message are just getting sent there but they're just queued up and don't get acted upon until Windows gets around to it (that's how multitasking operating systems work).
Siehe auch
Kategorien
Mehr zu Loops and Conditional Statements finden Sie in Help Center und File Exchange
Produkte
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!