MCI Functions, Macros, and Messages
Most MCI applications use the mciSendString
functions dozens of times. MCI provides some other useful functions that your
application will use less frequently.
The device identifier required by most MCI commands is typically retrieved in
a call to the open
) command. If you need a device identifier but do not want to open the device
for example, if you want to query the capabilities of the device before
taking any other action
you can call the mciGetDeviceID
function allows your application to use a device identifier to retrieve a
handle to the task that created that identifier.
You can use the mciGetYieldProc
functions to assign and retrieve the address of the callback function
associated with the "wait" (MCI_WAIT) flag.
function retrieves a string that describes an MCI error value. Each string
that MCI returns, whether data or an error description, is a maximum of 128
characters. Dialog box fields that are smaller than 128 characters will truncate the
longer strings returned by MCI. For more information about these strings, see Constants: MCIERR Return Values
The MCI macros are tools you can use to create and disassemble values that
specify time formats. These time formats are used in many MCI commands. The
formats acted on by the macros are hours/minutes/seconds (HMS),
minutes/seconds/frames (MSF), and tracks/minutes/seconds/frames (TMSF). The following table lists
the macros and their descriptions.
MCI also provides two messages: MM_MCINOTIFY
. The MM_MCINOTIFY message notifies an application of the outcome of an MCI
command whenever that command specifies the "notify" (MCI_NOTIFY) flag. The
MM_MCISIGNAL message is specific to digital-video devices; it notifies the
application when a specified position is reached.
- Software for developers
Software for Android Developers
- More information resources
Unix Manual Pages
- Databases for Amazon shops developers
Amazon Categories Database
Browse Nodes Database