User`s guide

8 Programming a GUIDE GUI
the programmatic uitable example “GUI that Dis plays a nd Graphs Tabular
Data” on page 15-19.
handles Structure
GUIDE creates a handles structure that contains the handles of all the
objects in the figure. For a GUI that contains an edit text, a panel, a pop-up
menu, and a push button, the
handles structure originally looks similar to
this. GU IDE uses each component’s
Tag property to name the structure
element for its handle.
handles =
figure1: 160.0 011
edit1: 9.0020
uipanel1: 8.001 7
popupmenu1: 7. 0018
pushbutton1: 16 1.00 11
output: 160.0 011
GUIDE creates and maintains the handles structure as GUI data. It is
passed as a n input argument to all callbacks and enables a GUI’s callbacks to
share property values and application data.
For information about GUI data, see “Ways to Manage Data in a GUIDE
GUI” on page 9-2 and the
guidata reference page.
For information about adding fields to the
handles structure and instructions
for correctly saving the structure, see “Adding Fields to the handles Structure”
on page 9-8 and “Changing GUI Data in a Code File Generated by GUIDE”
on page 9-9.
Changing Callbacks Assigned by GUIDE
As described in “Callback N ames and Signatures in GUIDE” on page 8-16,
GUIDE generates a name for a callback by concatenates the component’s
Tag
property (checkbox1) and its callback type. Although you cannot change a
callback’s type, you can change its
Tag, which will change the callback’s name
thenexttimeyousavetheGUI.
Change a component’s
Tag property to give its callbacks more meaningful
names; for example, you might change the
Tag property from check box1 to
8-22