Can not run a script
Mostra commenti meno recenti
I have a very simple GUI script, after I have run a few times, the run button become a 'gray pause' and the script can not be run again.

There is no error info in command window.
6 Commenti
Birdman
il 13 Dic 2017
Is there any infinite loop or buggy code in your GUI?
Henan
il 13 Dic 2017
Henan
il 15 Dic 2017
Image Analyst
il 15 Dic 2017
Can you also attach the .fig file so we can actually RUN this code?
By the way, how are you running this code? You're clicking on the green run triangle either in GUIDE or in the text editor, right? You're NOT double clicking the .fig file in the "Current folder" panel, are you? That won't work.
Henan
il 16 Dic 2017
Risposte (2)
Image Analyst
il 15 Dic 2017
Modificato: Image Analyst
il 15 Dic 2017
0 voti
Does the status bar in the lower left of the MATLAB window say "Busy"?
Try clicking in the command window and typing control-c a few times.
4 Commenti
Henan
il 16 Dic 2017
Image Analyst
il 16 Dic 2017
Look at the last line of your push button callback:
delete(gcf)
Exactly what do you think that will do? It will blow away your GUI. The Run button is back to a Run button. It does not turn into the grayed out Pause button. I know - I just tried it. The delete(gcf) will totally shut it down and return MATLAB to the initial condition before you even ran your GUI. If you don't want that to happen, get rid of the delete() function call.
Henan
il 17 Dic 2017
Image Analyst
il 17 Dic 2017
Well then it does that. It runs and closes itself down. I do not see the problem of the pause button showing. You'll have to call tech support because I can't reproduce your issue.
Jan
il 15 Dic 2017
'Enable','of'
This should cause an error message, because the value must be 'on' or 'off'. After this error, the GUI might stop to work. But I do not see, why the Run button is disabled then.
3 Commenti
Henan
il 17 Dic 2017
Jan
il 17 Dic 2017
A bold guess: Matlab is usually stable, but as an interpreted language it is susceptible for shadowing built-in functions. When the user redefines a toolbox function, the complete system can melt down. I have created a modified strcmp, which crashed. Afterwards I could neither open the file in the editor nor run rmpath or pathtool to remove this function, even closing Matlab did not work.
So check if you have shadowed an important built-in function: https://www.mathworks.com/matlabcentral/fileexchange/27861-uniquefuncnames . Never add user-defined folders on top of the path, but always at the bottom, to avoid this problem. Do not set the working directory to one of the toolbox folders, because this affects the precedence of functions.
But as usual for guessing: There is no evidence this this cause the problems you are faced with.
Jan
il 17 Dic 2017
This spelling mistake should let the code stop with an error message actually. You should have seen this when you try to run the code.
A bold guess: Matlab is usually stable, but as an interpreted language it is susceptible for shadowing built-in functions. When the user redefines a toolbox function, the complete system can melt down. I have created a modified strcmp, which crashed. Afterwards I could neither open the file in the editor nor run rmpath or pathtool to remove this function, even closing Matlab did not work.
So check if you have shadowed an important built-in function: https://www.mathworks.com/matlabcentral/fileexchange/27861-uniquefuncnames . Never add user-defined folders on top of the path, but always at the bottom, to avoid this problem. Do not set the working directory to one of the toolbox folders, because this affects the precedence of functions.
But as usual for guessing: There is no evidence this this cause the problems you are faced with.
Categorie
Scopri di più su Environment and Settings in Centro assistenza e File Exchange
Prodotti
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!