Problem with "dirty" GUI configuration

3 vues (au cours des 30 derniers jours)
Kristoffer Walker
Kristoffer Walker le 2 Déc 2019
Modifié(e) : Adam Danz le 3 Déc 2019
Folks,
I have developed a large GUI project using GUIDE. It is too large to convert to the new App Developer method of developing GUI's. Nonetheless, I'm asking for some tips on how to fix a dirty configuration issue. I modified the GUI *.fig while in debug mode. Specifically, I renamed tags on 2 editable text fields and scroll bars. I believe this somehow caused a corruption to occur. Now even if I delete the offending objects from the GUI *.fig, the file still will not save and I cannot seem to recover. Is there anyway that I may fix this? The error I get is shown below.
Thank you,
Kristoffer Walker
  10 commentaires
Adam Danz
Adam Danz le 3 Déc 2019
Modifié(e) : Adam Danz le 3 Déc 2019
Ha! I like the hashtag!
I wish there were an optional field when writing a question such as "Years of experience" so we know a little bit about the background of the person asking the question. But there are already a number of optional fields when writing the question that are commonly ignored. Matlab release number is one of them which is my biggest pet peeve when that info is missing and we later find out our solution doesn't work because the user doesn't have access to a new or updated function.
Kristoffer Walker
Kristoffer Walker le 3 Déc 2019
It's all good--more fields could be helpful, but sometimes simple is good too. Oh well, back to drinking my Matlab koolaid. :)

Connectez-vous pour commenter.

Réponse acceptée

Adam Danz
Adam Danz le 3 Déc 2019
These are the kinds of errors that happen when a GUI figure is edited from within GUIDE while the m-file is paused in debug mode or contains break points. First backup your m- and fig-files. Then make sure all breaks are cleared from the m-file (from the editor, go the breakpoints > clear all, or use dbclear). Close the m-file and the figure file. Try running the GUI again. You may have to make all of the changes again from within GUIDE.
The lesson is to never use GUIDE while the m-file is in debug mode or has breaks (better yet, close the m-file while editing the figure).

Plus de réponses (0)

Catégories

En savoir plus sur Migrate GUIDE Apps dans Help Center et File Exchange

Tags

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by