M:

main document file: The file currently interfaced to by an application's document. It can contain other files as embedded objects.; See also: document file
major build number: The number used to represent a significantly different software release e.g. in App 3.1, the major build number is 3.; See also: minor build number
makefile: A file containing all the information necessary to specify how to build projects in various environments; generated by build tools from a .mmp file.
Makesis: A program that uses a package file to create Symbian installation files (sis file).; See also: sis file package file
margins: A set of measurements (in twips), defining the insetting of the top, bottom, left and right edges of a rectangular object, e.g. a picture.; See also: picture
markup information: Information that is not part of a rich text object's text content, and which may be stored in a separate stream from the text. Consists of specific paragraph and character formatting, the style list, if owned by the object itself, and pictures. Fields are not markup information.; See also: specific formatting
mask: Bitmap defining transparent regions of another bitmap.
maximum length: The maximum length of data that a modifiable type descriptor is capable of holding.
mbm: File extension for the Symbian multi-bitmap file format.; See also: multi-bitmap file format
mbld file: File format used by the historical Menu builder tool.
MCF: Message Confirmation. Indicates that a complete message has been received and that additional messages may follow.
ME: Mobile Equipment. E.g. a mobile phone.
MEAD: Historical GUI tool that created the source, resource, makefiles and build configuration files for a generic Symbian application.
media: The media for storing information: may be a disk, a ROM, a flash RAM, etc; may be removable or non-removable; may be divided into one or more partitions.; See also: device partition
media server APIs: Historical component that provided audio and image manipulation. Replaced by the Multimedia Framework.
menu bar: A strip of menu headings normally hidden off-screen. The menu items on a menu bar send commands to an application when selected. An application's menu bar and the commands it sends, are defined in its resource file.; See also: command menu item
menu builder: Historical tool designed to assist developers in the creation of menu structures for Symbian applications.
menu item: An item on a menu bar. A menu item has an associated command.; See also: menu bar command
message: A data structure which the server uses to communicate with a client. It contains an opcode specifying the service request and a message argument array that is used when reading from and writing to the client.; See also: message argument array
message argument array: An array of pointers to message arguments in the client address space. This array is used by the kernel to create a message that facilitates reading and writing to the client from the server.; See also: message
Message Server: The server that maintains and controls access to all the entries within the messaging system.
Message Server session: The channel of communication between a client and the Message Server.
message service function: A member function in a server session (or object) class which implements the servicing of a specific message request from a client program.; See also: server-side session object
message slots: Determines the number of outstanding requests a client may have with a server at any one time.
message store: A Symbian OS direct file stream store associated with a Message Server entry that holds message body text, and protocol-specific data.
MIME: Multipurpose Internet Mail Extensions; first proposed in RFC 2045-2049, and continually updated by newer RFCs. A protocol whereby an Internet mail message can be composed of several independent items, including binary and application-specific data. Applications can register themselves as supporting particular MIME types.; See also: application capabilities
minor build number: The number used to represent a sub-release e.g. in App 3.1, the minor build number is 1.; See also: major build number
mixin: A historical synonym for an interface class.; See also: interface class
mixin protocol: A set of functions defining a protocol for interaction between one class and another. It can be defined by some virtual functions in a primary base class, or in a mixin class.; See also: interface class mixin
MMCA: MultiMediaCard Association. An international organization created to promote the adoption of the MultiMediaCard as the storage standard for telecommunications products.
MMP: Also known as project file. A hand-edited file whose main purpose is to specify the source files which go to make up a releasable. Used as an input to the build tools.
MMP file: Project definition file - specifies the properties of a project in a platform and compiler independent way.
MMU: Memory Management Unit, translates virtual to physical addresses and provides access permission control.
mobile country code: Uniquely identifies the country of domicile of the mobile subscriber.
mobile network code: Identifies the home GSM PLMN for the mobile subscriber.; See also: PLMN
model: Another word for an application engine.; See also: MVC engine
model: An object used to store the current state of an application or the file it is currently editing.; See also: app UI document
Model, View, Controller: A way of partitioning the design of software. The "model" is the internal workings of the program (the algorithms), the "view" is how the user sees the state of the model and the "controller" is how the user changes the state or provides input.; See also: MVC
modem connection status: Indicates whether the modem is connected or disconnected, or if the connection mode cannot be determined.
modifier changed event: An event generated by the window server when the state of one of the modifier keys changes.; See also: modifier key
modifier key: The SHIFT, CTRL and FN keys.
module definition file: File with .def extension, which specifies an ordinal value for each named function or data item to be exported from the DLL. It is used during an ordinal build to insert ordinal information into the DLL export table, allowing exports to be accessed by ordinal from user programs.; See also: DLL export ordinal build
mover: A control for moving other controls: dragging the pointer generates events to request the control's observer need to move. All dialogs contain a mover control.; See also: control
MPS: Multipage Signal. Indicates the end of a complete page of fax information, and to return to the beginning of phase C upon receipt of a confirmation.
MS: Mobile Station. This comprises the mobile equipment (usually a phone) and the SIM card.
MTM: Message type module: a group of components that together provide message handling for a particular protocol.
MTM component: A library that provides an implementation of an Client-side MTM, User Interface MTM, UI Data MTM, or Server-side MTM.
MTM type UID: UID that defines whether a particular MTM component is a Client-side MTM, User Interface MTM, UI Data MTM, or Server-side MTM.
multi-bitmap file format: Symbian OS bitmap file (.mbm) format.
multi-field numeric editor: A control that supports editing of a number of numeric fields.
MultiMediaCard: A data storage device providing small-size, high capacity data storage to handheld communication devices.
multiplexer: A device that combines several signals for transmission over a single medium.
Multipurpose Internet Mail Extensions: Also known as MIME.; See also: MIME
mutex: A Kernel object used to serialise access to a resource, which may be shared between threads across processes. Access to the mutex is through an RMutex handle.
MVC: Acronym for Model, View, Controller.; See also: Model View Controller