Thread Subject: Function questions

New member, so these questions have probably already been posed and answered.

I have been making a GUI, and I have run into several hangups:

1) Accessing data from other functions:

If i wrote a file like this:

%%%%%%%%%%%%%%%

function function1
f=figure('Name', 'Thing', 'Position', [1,1,500,500])
button1=uicontrol('Style', 'pushbutton', 'Callback',{@function2}, 'Position', [100,100,50,30])

button2=uicontrol('Style', 'pushbutton', 'Position', [200,100,50,30])


function function2(object, eventdata)
get(button1, 'Value')
externalprogram

%%%%%%%%%%%%%%%%

where externalprogram is an m-file like:

%%%%%%%%%%%%%%
x=5
%%%%%%%%%%%%%%

Then I get an error

??? Undefined function or variable 'button1'.

Error in ==> function1>function2 at 9
get(button1, 'Value')
??? Error while evaluating uicontrol Callback

as I should, since the functions have separate workspaces. I know there must be some way to interact with the workspace of function1 from within function2 without running function1 again. When you use GUIDE, there is a nifty get(handles.button1, 'Value') thing that you use, so I guess my question is, how do you construct this handles structure that lets you call on items in different workspaces?


2) If you close the functions as per above with "end"s and nest them, you can say get(button1,'Value'), but when externalprogram tries to run you get a different error:

??? Attempt to add "x" to a static workspace.
 See MATLAB Programming, Restrictions on Assigning to Variables for details.

??? Attempt to add "x" to a static workspace.
 See MATLAB Programming, Restrictions on Assigning to Variables for details.

Error in ==> externalprogram at 1
x=5
Error in ==> function1>function2 at 10
externalprogram

??? Error while evaluating uicontrol Callback

I understand that there is rule that does not allow variables to be added dynamically in a nested function, but there must be a way around this without copying and pasting the code from the external file inside the nested function. It is desirable to be able to cause another program to run inside the function, and a program isn't much good if it can't manipulate variables.

So how do I make this work?


I appreciate the help guys, and apologize for a long post or if I have asked a frequently asked question. I think once I understand these questions I will be much better off!

"Johnathan " <durchfalldurchfall@yahoo.com> wrote in message
news:gu3a8b$pet$1@fred.mathworks.com...
> New member, so these questions have probably already been posed and
> answered.
>
> I have been making a GUI, and I have run into several hangups:
>
> 1) Accessing data from other functions:
>

... SNIP

Hi Johnathan,

I think the questions you are asking are answer in this good web page on
programming the GUI.

http://www.mathworks.com/access/helpdesk/help/techdoc/index.html?/access/helpdesk/help/techdoc/&http://www.mathworks.com/support/product/product.html?product=ML

hope this helps.

--Nasser

"Nasser Abbasi" <nma@12000.org> wrote in message <fmaNl.16319$pr6.1809@flpi149.ffdc.sbc.com>...

Nasser, unfortunately that link doesn't take me anywhere but the first page of the help manual.

I have read many help manual pages but have not figured it out, and if you have time I would really appreciate it if you could help me out more specifically as per the example I gave.

Thank you for the help!

I keep this message for copy and past now and then:

Functions in GUI, like any other functions, have their own private workspace. They are not shared, and they are clear when the (nested) function ends.

To pass data among functions in Gui (it can be many guis), we have to use one of these options:

- GUIDATA
- SET/GETAPPDATA
- SET/GET on the field USERDATA of graphic handles of your GUI
- GLOBAL variables
- ASSIGNIN/EVALIN

The first ones are preferred methods. The two last are to be avoided.

Bruno

"Bruno Luong" <b.luong@fogale.findmycountry> wrote in message <gu3c4a$ob1$1@fred.mathworks.com>...
> I keep this message for copy and past now and then:
>
> Functions in GUI, like any other functions, have their own private workspace. They are not shared, and they are clear when the (nested) function ends.
>
> To pass data among functions in Gui (it can be many guis), we have to use one of these options:
>
> - GUIDATA
> - SET/GETAPPDATA
> - SET/GET on the field USERDATA of graphic handles of your GUI
> - GLOBAL variables
> - ASSIGNIN/EVALIN
>
> The first ones are preferred methods. The two last are to be avoided.
>
> Bruno

I see now how to transfer data with guihandles:

function function1
f=figure('Name', 'Thing', 'Position', [1,1,500,500]);

button1=uicontrol('Style', 'pushbutton', 'Callback',{@function2}, 'Position', [100,100,50,30]);

button2=uicontrol('Style', 'pushbutton', 'Position', [200,100,50,30], 'Callback',{@function3});

myhandles=guihandles(f);
myhandles.button1.string='boy';
guidata(f,myhandles);

function function2(object, eventdata)
myhandles=guidata(gcbo);
myhandles.button1.string
set(button1,'String',myhandles.button1.string)
% = gcbo returns the handle of the graphics object whose callback is executing.
%[h,figure] = gcbo returns the handle of the current callback object and the handle of the figure containing this object.
myhandles.button1.string='dog';
guidata(gcbo,myhandles);
end

function function3(object, eventdata)
myhandles=guidata(gcbo);
set(button1,'String',myhandles.button1.string)
myhandles.button1.string
end
end



when I press button 1:
ans =
boy
and button 1 now says boy

when I press button 2:
ans =
dog
and button 1 now says dog


Is it possible to create this type of structure which is accessible to multiple functions without using guihandles, as in from the struct data type? This only works when associated with a figure. If not, would it be advisable to use non-visible figures to pass data between functions in a non-GUI related program?

Also, what exactly is this doing? Is it saving your information to the temporary figure file and then reading it when you use guidata? Would it be a bad idea to use an external .txt or other file to pass information from program to program or function to function, or is there another way to do it? Is this common practice?

Thanks guys,
John

also, I am still at a loss with the adding variables dynamically thing. If I nest the functions as per above, then I really need to figure that one out!

>
>
> Is it possible to create this type of structure which is accessible to multiple functions without using guihandles, as in from the struct data type? This only works when associated with a figure. If not, would it be advisable to use non-visible figures to pass data between functions in a non-GUI related program?

Why such a need? Non GUI program are usually in the same thread, no callback or timer involved, linearly performed. So just create your structures and pass them among functions as input arguments. Function parameter is designed for that, abuse it.

>
> Also, what exactly is this doing? Is it saving your information to the temporary figure file and then reading it when you use guidata?

There is no file involved.

> Would it be a bad idea to use an external .txt or other file to pass information from program to program or function to function, or is there another way to do it? Is this common practice?

Yes it's a bad idea using file. Just use function parameters as commonly practiced. What is the fear of it??? Such strange question.

Bruno

In article <gu3c4a$ob1$1@fred.mathworks.com>,
b.luong@fogale.findmycountry says...
> I keep this message for copy and past now and then:
>
> Functions in GUI, like any other functions, have their own private workspace. They are not shared, and they are clear when the (nested) function ends.
>
> To pass data among functions in Gui (it can be many guis), we have to use one of these options:
>
> - GUIDATA
> - SET/GETAPPDATA
> - SET/GET on the field USERDATA of graphic handles of your GUI
> - GLOBAL variables
> - ASSIGNIN/EVALIN
>
> The first ones are preferred methods. The two last are to be avoided.
>
> Bruno
>

Another option: use nested functions.

--
Loren
http://blogs.mathworks.com/loren

Loren Shure <loren@mathworks.com> wrote in message <MPG.2471dc3ebd35e04898999e@news.mathworks.com>...
> In article <gu3c4a$ob1$1@fred.mathworks.com>,
> b.luong@fogale.findmycountry says...
> > I keep this message for copy and past now and then:
> >
> > Functions in GUI, like any other functions, have their own private workspace. They are not shared, and they are clear when the (nested) function ends.
> >
> > To pass data among functions in Gui (it can be many guis), we have to use one of these options:
> >
> > - GUIDATA
> > - SET/GETAPPDATA
> > - SET/GET on the field USERDATA of graphic handles of your GUI
> > - GLOBAL variables
> > - ASSIGNIN/EVALIN
> >
> > The first ones are preferred methods. The two last are to be avoided.
> >
> > Bruno
> >
>
> Another option: use nested functions.
>

And to pass the nested function handle around, use... the above of course

Bruno