Changing Homer GUI Code
Revision as of 13:48, 14 August 2008 by Dean Whittaker (talk | contribs)
The homer GUI is designed to be compiled into a standalone application. This task is performed by the function
- >> homer_compile
dos and don'ts
There are a few rules when altering code that 'MUST' be obeyed, these are:
* NO feval or eval statements - these do not compile * Folder names MUST be stored without a slash at the end, i.e. '..\libisis\matlab' is ok, but '..\libisis\matlab\' is not. * Use the command filesep to get the folder separator for the current platform instead of using '\' * Do not use script mfiles * Use text files for any optional settings etc. so that a user may change them once the suite has been compiled * Always include the mcrinstaller with any distribution
How To Compile
- run homer_compile
- copy the folder "instrument_setup" to the same folder that the package compiled to (typically c:/stand_alone_homer)
- insure that mcrinstaller.exe is in the folder that the package compiled to