Figures

Figures are the windows that contain the GUIs you design with the Layout Editor. See the Figure Properties reference page for information on what figure characteristics you can control.

Displaying Plots in a Separate Figure

To prevent a figure from becoming the target of plotting commands issued at the command line or by other GUIs, you can set the HandleVisibility and IntegerHandle properties to off. However, this means the figure is also hidden from plotting commands issued by your GUI. To issue plotting commands from your GUI,

• Create a figure and axes.

• Save the handle of the figure in the handles structure.

• Create an axes, save its handle, and set its Parent property to the figure handle.

• Create the plot, save the handles, and set their Parent properties to the handle of the axes.

The following code illustrates these steps:

fHandle =

figure('HandleVisibility','off','IntegerHandle','off',...

'Visible','off');

aHandle = axes('Parent',fHandle);

pHandles = plot(PlotData,'Parent',aHandle);

set(fHandle,'Visible','on')

Note that not all plotting commands accept property name/property value specifications as arguments. Consult the reference page for the specific command to see what arguments you can specify.

Managing gui Data with the Handles Structure

GUIDE provides a mechanism, called the handles structure, for storing and retrieving shared data using the same structure that contains the GUI component handles. The handles structure, which contains the handles of all the components in the GUI, is passed to each callback in the GUI M-file. Therefore, this structure is useful for saving any shared data. The following example illustrates this technique.

If you are not familiar with MATLAB structures, see Structures for more information. This section covers the following topics:

• Example: Passing Data Between Callbacks

• Application Data

Example: Passing Data Between Callbacks

This example demonstrates how to use the handles structure to pass data between callbacks. The example passes data between a slider and an editable text box in the following way:

• When a user moves the slider, the text box displays the slider's current value.

• When a user types a value into the text box, the slider updates to this value.

• If a user enters a value in the text box that is out of range for the slider -- that is, a value that is not between 0 an 1 -- the application returns a message indicating how many times he has entered an erroneous value.

The following figure shows the GUI with a static text field above the edit text box.

Defining the Data Fields in the Opening Function

The GUI records the number of times a user enters an erroneous value in the text box and stores this number in a field of the handles structure. You can define this field, called number_errors, in the opening function as follows:

handles.number_errors = 0;

Type this command before the following line, which GUIDE automatically inserts into the opening function.

guidata(hObject, handles); % Save the updated structure

The guidata command saves the handles structure so that it can be retrieved in the callbacks. Note To save any changes that you make to the handles structure, you must add the command guidata(hObject, handles) following the code that implements the changes.

Setting the Edit Text Value from the Slider Callback

The following command in the slider callback updates the value displayed in the edit text when a user moves the slider and releases the mouse button.

set(handles.edit1,'String',...

num2str(get(handles.slider1,'Value')));

The code combines three commands:

• The get command obtains the current value of the slider.

• The num2str command converts the value to a string.

• The set command resets the String property of the edit text to the updated value.

Setting the Slider Value from the Edit Text Callback

The edit text callback sets the slider's value to the number the user types in, after checking to see if it is a single numeric value between 0 and 1. If the value is out of range, then the error count is incremented and the edit text displays a message telling the user how many times they have entered an invalid number.

val = str2double(get(handles.edit1,'String'));

% Determine whether val is a number between 0 and 1

if isnumeric(val) & length(val)==1 & ...

val >= get(handles.slider1,'Min') & ...

val <= get(handles.slider1,'Max')

set(handles.slider1,'Value',val);

else

% Increment the error count, and display it

handles.number_errors = handles.number_errors+1;

guidata(hObject,handles); % store the changes

set(handles.edit1,'String',...

['You have entered an invalid entry ',...

num2str(handles.number_errors),' times.']);

end

If the user types a number between 0 and 1 in the edit box and then clicks outside the edit box, the callback sets handles.slider1 to the new value and the slider moves to the corresponding position.

If the entry is invalid -- for example, 2.5 -- the GUI increments the value of handles.number_errors and displays a message like the following: