Thread Subject: gui .m file referencing functions in older version instead of own

I made a gui using guide (call it mygui with .m file mygui.m) and then revised it and called it mygui2 (with .m file mygui2.m). However, when I run mygui2, instead of calling its own functions, it calls functions from mygui (which are called the same thing). For some reason, it is not giving its own namespace priority. I don't have much experience putting multiple functions in a single .m file, so I don't know whether this is just what matlab does, but it would seem intuitive to give the functions in one's own .m file priority.

Other than the easy but annoying fix of naming all the functions differently (although I haven't tried this to make sure it would work), is there anything else to be done?
Thanks,
Scott

version: 2007b
os: win

"scott" <grenblau@yahoo.deletethis.com> wrote in message <h1ig0e$s6k$1@fred.mathworks.com>...
> I made a gui using guide (call it mygui with .m file mygui.m) and then revised it and called it mygui2 (with .m file mygui2.m). However, when I run mygui2, instead of calling its own functions, it calls functions from mygui (which are called the same thing). For some reason, it is not giving its own namespace priority. I don't have much experience putting multiple functions in a single .m file, so I don't know whether this is just what matlab does, but it would seem intuitive to give the functions in one's own .m file priority.
>
> Other than the easy but annoying fix of naming all the functions differently (although I haven't tried this to make sure it would work), is there anything else to be done?
> Thanks,
> Scott

The "cause" probably does not lie on your mfile but the associated fig file. Each graphic object has its own callback property and probably they are still refering to the inner function of mygui(). It's usually not recommend to "revise" a GUI file, whatever "revise" mean.

Bruni

On Jun 20, 4:09 am, "scott" <grenb...@yahoo.deletethis.com> wrote:
> I made a gui using guide (call it mygui with .m file mygui.m) and then revised it and called it mygui2 (with .m file mygui2.m).  However, when I run mygui2, instead of calling its own functions, it calls functions from mygui (which are called the same thing).  For some reason, it is not giving its own namespace priority.  I don't have much experience putting multiple functions in a single .m file, so I don't know whether this is just what matlab does, but it would seem intuitive to give the functions in one's own .m file priority.
>
> Other than the easy but annoying fix of naming all the functions differently (although I haven't tried this to make sure it would work), is there anything else to be done?
> Thanks,
> Scott
>
> version: 2007b
> os: win

What you would want to do instead is save the .fig file as mygui2, it
will automatically name the new .m file accordingly and fix and
linking issues.
This has happened to me too, and that's what solved it.
Good luck
-Nathan

Nathan <ngreco32@gmail.com> wrote in message <0ad1b602-3b0b-4d4a-b819-d30be043ae1b@y10g2000prc.googlegroups.com>...
> On Jun 20, 4:09?am, "scott" <grenb...@yahoo.deletethis.com> wrote:
> > I made a gui using guide (call it mygui with .m file mygui.m) and then revised it and called it mygui2 (with .m file mygui2.m). ?However, when I run mygui2, instead of calling its own functions, it calls functions from mygui (which are called the same thing). ?For some reason, it is not giving its own namespace priority. ?I don't have much experience putting multiple functions in a single .m file, so I don't know whether this is just what matlab does, but it would seem intuitive to give the functions in one's own .m file priority.
> >
> > Other than the easy but annoying fix of naming all the functions differently (although I haven't tried this to make sure it would work), is there anything else to be done?
> > Thanks,
> > Scott
> >
> > version: 2007b
> > os: win
>
> What you would want to do instead is save the .fig file as mygui2, it
> will automatically name the new .m file accordingly and fix and
> linking issues.
> This has happened to me too, and that's what solved it.
> Good luck
> -Nathan


Thanks for your suggestion. I did this, but am still getting the problem.

For example, here is an error message from the following situation.

I had a .fig file named fixSpotCalls.fig
I generated fixSpotCalls.m from it.
I edited fixSpotCalls.fig to fixSpotCallsRFOnly.fig and generated a new .m file called fixSpotCallsRFOnly.m

Then I ran fixSpotCallsRFOnly and here is the error messasge when trying to create one of the ui controls.

---------------
q=fixSpotCallsRFOnly('tmr','001',w);
??? Undefined function or method 'fixSpotCalls' for input arguments of type 'char'.

Error in ==> @(hObject,eventdata)fixSpotCalls('spotContextSlider_CreateFcn',hObject,eventdata,guidata(hObject))


??? Error using ==> struct2handle
Error while evaluating uicontrol CreateFcn
-------------------------
In the properties for this uicontrol, however, I have the following under createfcn:

fixSpotCallsRFOnly('spotContextSlider_CreateFcn',gcbo,[],guidata(gcbo))

which is correct.



Thanks,
Scott

One more thing I forgot to mention. The reason it gave me an error in createfcn is because I renamed the old fixSpotCalls.fig and fixSpotCalls.m files to something else so that they could no longer be found. This exposed the embedded dependence upon those files in my new fixSpotCallsRFOnly.m/fig files

"scott" <grenblau@yahoo.deletethis.com> wrote in message <h1mvi7$bk$1@fred.mathworks.com>...
> One more thing I forgot to mention. The reason it gave me an error in createfcn is because I renamed the old fixSpotCalls.fig and fixSpotCalls.m files to something else so that they could no longer be found. This exposed the embedded dependence upon those files in my new fixSpotCallsRFOnly.m/fig files

Take a look of the CALLBACK in your fig, as we suggested.

Bruno