GUI FIG-Files and M-files GUI FIG-Files and M-Files GUidE stores GUIs in two files, which are generated the first time you save or run the gui FIG-file-a file with extension. fig that contains a complete description of the GUi figure layout and the components of the GUI: push buttons, menus axes, and so on. When you make changes to the GuI layout in the layout Editor, your changes are saved in the FIg-file M-file- a file with extension m that contains the code that controls the GUl, including the callbacks for its components. This file is referred to as the GUI M-file. When you first run or save a gUI from the Layout Editor GUidE generates the GuI M-file with blank stubs for each of the callbacks You can than program the callbacks using the M-file editor Note In the documentation for releases prior to Release 13, the GUI M-file was referred to as the“ application M-file.”GUI FIG-Files and M-Files 1-5 GUI FIG-Files and M-Files GUIDE stores GUIs in two files, which are generated the first time you save or run the GUI: • FIG-file — a file with extension .fig that contains a complete description of the GUI figure layout and the components of the GUI: push buttons, menus, axes, and so on. When you make changes to the GUI layout in the Layout Editor, your changes are saved in the FIG-file. • M-file — a file with extension .m that contains the code that controls the GUI, including the callbacks for its components. This file is referred to as the GUI M-file. When you first run or save a GUI from the Layout Editor, GUIDE generates the GUI M-file with blank stubs for each of the callbacks. You can than program the callbacks using the M-file editor. Note In the documentation for releases prior to Release 13, the GUI M-file was referred to as the “application M-file