Display and user interface of nine functions of brew SDK

The screen display in brew is mainly implemented by the idisplay interface. With idisplay, you can write text, draw pictures, draw straight lines, and some simple geometric figures. If you want to draw complex ry or line, you have to turn to the igraphics interface. Idisplay is used by all applications. during use, you do not need to create it explicitly. The system will automatically create it unless you want to implement multi-video memory processing. Idisplay allows you to control the backlight and annunciators of the device. After brew3.x, the backlight of the device can be separately controlled through the ibacklinght interface.

The UI interface controls in brew are derived from the iControl interface, as shown in the relationship between them.

Figure 11-1: iControl-based Display Control

 
 

Istatic is equivalent to the static text box control in MFC. It is used to display uneditable text/simple image information. It supports line breaks, automatic scrolling, and decorative attribute display.

Imenuctl is a menu control. The so-called menu should allow users to browse all menu options available by pressing the "up", "down", "Left", and "right" keys, the options selected by the user are separated from other options. When you press the "select" key, the evt_command event will be sent back to your application.ProgramEvent processing functions. Imenuctl supports four menu formats:

Standard menu, classid: aeeclsid_menuctl

List menu, classid: aeeclsid_listctl

Software menu, classid: aeeclsid_softkeyctl

Icon menu, classid: aeeclsid_iconviewctl

Itextctl is equivalent to the text box in MFC, providing data input for users. The text control allows the device user to input text strings by pressing a key on the device. The text control consists of an optional title and a rectangle window. The window contains one or more lines of input text displayed to the user. The text control converts the user's key operations to characters. The application only needs to pass the key event to the activated text control and obtain the text from the control when the device user completes text input. The conversion process depends on the text input modes supported by the device, such as the standard multiple-key mode (selected by the device user from the characters mapped to each key) and the T9 Lenovo text input mode. If multiple text input modes are supported, the application enables the device user to select the specified mode when activating the text control. The text control allows you to specify a soft key menu for this purpose. When activating a text control, the application must send all key events to it by calling itextctl_handieevent.

 

This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/wireless_com/archive/2010/03/31/5435836.aspx