Matlab的GUI回调函数

Kinds of CallbacksThe following table lists the callback properties that are available, their triggering events, and the components to which they apply.Note：User interface controls include push buttons, sliders, radio buttons, check boxes, editable text boxes, static text boxes, list boxes, and toggle buttons. They are sometimes referred to as uicontrols.GUIDE Callback ArgumentsAll callbacks in a GUIDE-generated GUI code file have the following standard input arguments:hObject —Handle of the object, e.g., the GUI component, for which the callback was triggered. For a button group SelectionChangeFcn callback, hObject is the handle of the selected radio button or toggle button.eventdata — Sequences of events triggered by user actions such as table selections emitted by a component in the form of a MATLAB struct (or an empty matrix for components that do not generate eventdata)handles — A MATLAB struct that contains the handles of all the objects in the GUI, and may also contain application-defined data. See handles Structure for information about this structure.Object HandleThe first argument is the handle of the component issuing the callback. Use it to obtain relevant properties that the callback code uses and change them as necessary. For example,theText = get(hObject,'String');places the String property (which might be the contents of static text or name of a button) into the local variable theText. You can change the property by setting it, for exampleset(hObject,'String',date)This particular code changes the text of the object to display the current date.Event DataEvent data is a stream of data describing user gestures, such as key presses, scroll wheel movements, and mouse drags. The auto-generated callbacks of GUIDE GUIs can access event data for Handle Graphics® and uicontrol and uitable object callbacks. The following ones receive event data when triggered:CellEditCallback in a uitableCellSelectionCallback in a uitableKeyPressFcn in uicontrols and figuresKeyReleaseFcn in a figureSelectionChangeFcn in a uibuttongroupWindowKeyPressFcn in a figure or any of its child objectsWindowKeyReleaseFcn in a figure or any of its child objectsWindowScrollWheelFcn in a figureEvent data is passed to GUIDE-generated callbacks as the second of three standard arguments. For components that issue no event data the argument is empty. For those that provide event data, the argument contains a structure, which varies in composition according to the component that generates it and the type of event.For example, the event data for a key-press provides information on the key(s) currently being pressed. Here is a GUIDE-generated KeyPressFcn callback template:% --- Executes on key press with focus on checkbox1 and none of its controls.function checkbox1_KeyPressFcn(hObject, eventdata, handles)% hObject handle to checkbox1 (see GCBO)% eventdata structure with the following fields (see UICONTROL)% Key: name of the key that was pressed, in lower case% Character: character interpretation of the key(s) that was pressed% Modifier: name(s) of the modifier key(s) (i.e., control, shift) pressed% handles structure with handles and user data (see GUIDA TA)The eventdata structure passed in has three fields, identifying the Character being pressed (such as '='), the key Modifier (such as 'control'), and the Key name (spelled out, such as 'equals'). Components that provide event data use different structures with event-specific field names to pass data. Callbacks with event data usually are repeatedly issued as long as the event persists or sometimes at the beginning of an event and thereafter only when its values change.Learn how callbacks use event data by looking at the GUIDE uitable example GUI to Interactively Explore Data in a Table (GUIDE) and the programmatic uitable example GUI that Displays and Graphs Tabular Data.handles StructureGUIDE 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. GUIDE uses each component's Tag property to name the structure element for its handle.handles =figure1: 160.0011edit1: 9.0020uipanel1: 8.0017popupmenu1: 7.0018pushbutton1: 161.0011output: 160.0011GUIDE creates and maintains the handles structure as GUI data. It is passed as an 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 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 and Changing GUI Data in a Code File Generated by GUIDE.。