Universal Asynchronous Receiver/Transmitter. Common name for the hardware that drives an RS232 serial port.
See also: RS232
A framework for creating user interface controls; a framework for applications to handle user interface events; and environment utilities for control creation and access to windowing functionality.
A component that provides user interface resources for a particular messaging protocol.
The central user interface class. It creates and owns controls to display the application data, and centralises handling of command input from standard controls such as menus and toolbars. The app UI base class is provided by CEikAppUi, which can be customised by using the resource structure EIK_APP_INFO.
A UID, or "Unique Identifier", is a globally unique 32-bit number used in a compound identifier to uniquely identify an object, file type, etc.
When users refer to "UID" they often mean UID3, the identifier for a particular program.
See also: UID typeUID1, UID2, UID3, compound identifier
A set of three UIDs which, in combination, identify an EPOC object; encapsulated by a TUidType
.
See also: UID1, UID2, UID3
The first UID in a compound identifier (UID type). It identifies the general type of an EPOC object and can be thought of as a system level identifier; for example executables, DLLs, and file stores are all distinguished by UID1.
See also: UID, UID type, UID2, UID3
The second UID in a compound identifier (UID type). It; distinguishes within a type (i.e. within a UID1), and can be thought of as an interface identifier. For example static interface (shared library) and polymorphic interface (application or plug-in framework) DLLs are distinguished by UID2.
See also: UID, UID type, UID1, UID3
The third UID in a compound identifier (UID type). It identifies a particular subtype and can be thought of as a project identifier (for example UID3 might be shared by all objects belonging to a given program, including library DLLs if any, framework DLLs, and all documents).
See also: UID, UID type, UID1, UID2
ISO 10646-1 defines a "universal character code" which uses either 2 or 4 bytes to represent characters from a large character set. Thus, Far Eastern character sets can be represented.
In EPOC, 2-byte UNICODE support is built deep into the system.
In the context of an agenda entry, thus uniquely identifies an agenda entry or to-do list in an agenda file. This value is assigned when the entry or to-do list is created, and is preserved during updates. Because of this, it can be used to identify the entry or to-do list during synchronisation.
See also: entry ID
A piece of hardware on which a device may be found.
The system time, equivalent to GMT.
See also: local time
The offset in seconds from the universal time.
See also: universal time
Untimed alarms are associated with untimed Agenda entries. The alarm time is independent of the time of the entry with which it is associated.
See also: Timed alarm, clock alarm, orphan alarm, snoozed alarm, session alarm
Window Server : An event of type Button1Up, Button2Up or Button3Up. The user actions that result in these events will vary depending on the type of pointing device: mouse, pen, etc.
The layer of controls, editors and dialogs which allows a user to control a running application. In EIKON, user commands are handled by a subclass of CEikAppUi
.
See also: application, command
A component that provides user interface functions for a particular messaging protocol.
Universal Time Co-ordinated. The UTC offset is the same as the GMT offset.
Utility classes provide easy access for applications to frequently-used functionality. Notable files are EikFileUtils for file access, and EikResourceUtils for resource access.