Prev: spirals and knots
Next: Passing argument between functions
From: David Gathright on 18 Jun 2008 19:41
I have a GUI I've created using GUIDE, but I moved the .m
and .fig files to a new directory (made more sense for
organization in code repository). Now I cannot open the
file in GUIDE because it is apparently looking in it's
history for any 'existing' GUIs. If I try to open the .fig
file, it simply executes the .m file and does not open the
GUI in GUIDE.

I can think of several other reasons how one could get into
this state other than moving files around--for example:
What if I develop this GUI and then pass it off to someone
else to maintain? Or, what if my computer crashes hard and
I have to re-install everything?

I was finally able to open my existing GUI by creating a
new, blank GUI (so that GUIDE actually opens), then using
the 'Open' feature within the GUIDE window, which lets you
browse your file heirarchy.

So that this workaround isn't necessary, the 'Open Existing
GUI' tab in the initial GUIDE window should have a 'browse'
feature (in addition to the history, which is very useful
in other cases).

Anyway, I hope this helps someone else. Silly me, I wasted
15 minutes trying to do this the hard way (by locating the
GUI 'history' and editing it--never did find it, either).

DSG
From: Nick on 18 Jun 2008 15:59
Open up a new GUI in guide, and then use the 'open' option in the guide menu to open your old GUI.
 | 
Pages: 1
Prev: spirals and knots
Next: Passing argument between functions