Texas Instruments TI89 Developer Guide - Page 1100

1058 Appendix A: System Routines - Text Editing TE_handleEvent Declaration: Category(ies): Description: Inputs: Outputs: Assumptions: Side Effects: Availability: BOOL TE_handleEvent (TERecord * teRec, Event * e) Text Editing This routine is the text editor's event handler. Keypresses, cursor blink, cut, copy and paste operations, displaying and scrolling text, and other details of interpreting the interaction between the user and text edit fields are handled by this routine. Applications using the text edit manager typically process events in three phases. In phase one, the application examines the event for action it needs to take. Either the application handles the event and returns to the event manager or it proceeds to phase two. In phase two, the application calls TE_handleEvent to allow the text edit manager to process the event. Either TE_handleEvent handles the event and returns function value TRUE, or it does not understand the event and returns FALSE. If TE_handleEvent does not handle the event, the application proceeds to phase three. In phase three, the application calls EV_defaultHandler to let the event manager have one last try at handling the event. System-wide default behavior is implemented in EV_defaultHandler. teRec - The state record of a text edit field. e - An event message received from the event manager. Applications may drive the text editor by calling TE_handleEvent with their own created event messages, but in practice, the application just forwards events it received from the event manager. Returns TRUE if the text edit manager handled the event. Returns FALSE if the text edit manager did not understand the event and consequently did not process the event. teRec must have been initialized by a prior call to TE_open, TE_openFixed, or TE_reopen. The heap may be compressed. All versions of the TI-89 / TI-92 Plus. (continued) TI-89 / TI-92 Plus Developer Guide Not for Distribution Beta Version January 26, 2001