You can openfig() the fig file and assign the result (figure number) to a variable, and
findall(FigureNumber, 'type', 'uicontrol', 'style', 'pushbutton')
This will return handles to all of the pushbuttons. You can then examine their properties such as String to locate the one you want. That handle will have a callback property that will contain an anonymous function in which you will be able to see the function being invoked. It will look something like
@(hObject, event) GUINAME('FUNCTIONNAME', hObject, event, handles(gcbo))
You need the gui name and function name from that, and you need unique identifying information about the button, with it being quite likely that the button Tag will be unique.
Now, the process of "clicking" the button is:
- run the gui by name, recording the figure handle returned. It is possible that the gui does not return until you quit the gui: if so then that complicates matters, potentially even too much for this general strategy to be used, but other times just a durned nuisance.
- assuming that the figure handle was returned, use findall() on it with the identifying information determined earlier, probably the Tag, to get the handle to the button object
- when it is time to "click" the button, first set the Value property of the button to 1
- then call GUINAME('FUNCTIONNAME', buttonhandle, [], handles(buttonhandle)) where GUINAME and FUNCTIONNANE are copied from your investigation
- then set the button handle Value back to 0
The exact sequence of steps I give here would need to be modified if the gui is sufficiently old that the Callback was not an anonymous function and was instead a character vector
If the gui does not return until it is quit then you have a challenge on your hands of needing to initialize the gui without calling the OpenFcn callback. The OpenFcn could potentially be spring loaded to set variables in ways that could be detected by the code to validate that regular initialization was done, if the gui went to enough trouble.
