Carrying variables and matrices between GUIs

Hello,

Is there a way to carry variable between GUIs. I am calling a GUI inside another GUI. I want to carry variables from the first on to the second one. For example

   First GUI
  Function1
  Function2
  .
  .
  .
  Call the second GUI ( I want to access some of the results from above functions) and I don't want to save and load the data.

Is there a way of doing this?

Thanks

Answer 1

[Walter Roberson]

Yes, a GUI is a function, and you can define the function with as many parameters as you need and pass the parameters from the first GUI.

But see also http://matlab.wikia.com/wiki/FAQ#How_can_I_share_data_between_callback_functions_in_my_GUI.3F

Answer 2

[Image Analyst]

Just pass them in the argument list.

function FirstGUI()
  % Call a couple of functions defined inside FirstGUI.m
  Function1();
  Function2();
  % Now, call the the second GUI, passing it some arguments...
  [output1, output2] = SecondGUI(input1, input2, input3);

In the OpeningFcn() of the second GUI, look at varargin to extract the various inputs and do something with them, like send their values to properties of various widgets on the interface, or whatever you want.

[Kamuran]

Thanks, I am able to carry the variables, data to SecondGUI's OpeningFcn using varargin. But I can't see the data outside the OpeningFcn()

    OpeningFcn(hObject, eventdata, handles, input1, input2, input3)
    ALL_input=[ input1 input2 input3]; % I collect them in one matrix

and I want to reach that data in function pushbutton_Callback function.

I used setappdata(0,'My_DATA',ALL_input); inside OpeningFnc and getappdata(0,'My_DATA') in pushbutton did not work.

Do you have a solution for this one too?

Thanks for the help

[Jan]

@Kamuran: Please explain "did not work" with any details.

[Kamuran]

setappdata worked. I just forget to name my getappdata part.

I did ALL_input=getappdata(0,'My_DATA')

Thanks for the help

[Walter Roberson]

Why not pass them all in one matrix in the first place?

If the matrices might be different size or data types, use a cell array instead of a numeric array. or use a structure.

varstopass = struct{'input1', input1, 'input2', input2, 'input3', input3);

then pass in varstopass, and afterwards you can use varstopass.input1 and so on.

[Image Analyst]

Good idea, and that's what I do. Any user settings that I need to pass around to different functions (ones that are not simply GUI properties), I just attach as fields to a structure I call UserSettings and then pass that around. The Mathworks recommends attaching to the "handles" structure but the handles structure already has so many other things on it that I don't want to clutter it up with my stuff.