The file standard_fig.m only exists as a "path" to the actual gui figure file. The contents of the file itself are irrelevant.
I normally leave all of the event handles in that file blank, to avoid confusion. establishing your own event handlers in your class function will overwrite any existing ones in the fig.m file. However, I am uncertain what will happen to events that are not rewritten. The 2 possibilities are that they exists and could still be used, or that they are completely ignored.
When I get a change, I will run a test to see what happens and reply again.
im working on making a gui as a class object, and i have a question about your code. is it necessary to write the functionality of the callback functions in standard_fig.m as well as in the mapped class function? this seems to add room for error with duplicate code. thanks!
10 May 2014
Like subplot, but easier, and WYSIWYG export to file. Also fixes dashed/dotted lines in export.
Thanks for the ideas Ben, not all the functions return handles :-(, but for those that do your idea is that I let the external function create the axes "free", then set up my panels, then use .select(axis_handle) to capture the axis into the correct panel -- I hadn't thought of it that way as I normally always select() before I plot. Will give this a go when I get time. Thanks again for a such a useful utility!!!
p.s. and yes the various website bugs on FEX are annoying, I normally copy my text before submitting just in case here...