Jump to content

MM MCIEVENT: Difference between revisions

From EDM2
Created page with "{{DISPLAYTITLE:MM_MCIEVENT}} This message notifies an application of an event generated by a device. ==Syntax== <PRE> MsgParam1 USHORT usEventCode; Device-specific event code.: USHORT usDeviceID; Device ID.: MsgParam2 PVOID pEventData; Device-specific event data.: </PRE> ==Parameters== ;''usEventCode'' (USHORT) - input :Device-specific event code. The following event notification codes are currently defined: :* '''MCI_MIXEVENT''' A mixer attri..."
 
(No difference)

Latest revision as of 03:00, 26 November 2025

This message notifies an application of an event generated by a device.

Syntax

MsgParam1
USHORT usEventCode;  /* Device-specific event code. */
USHORT usDeviceID;   /* Device ID. */

MsgParam2
PVOID pEventData;    /* Device-specific event data. */

Parameters

usEventCode (USHORT) - input
Device-specific event code. The following event notification codes are currently defined:
  • MCI_MIXEVENT A mixer attribute has changed.
usDeviceID (USHORT) - input
Device ID.
pEventData (PVOID) - input
Device-specific event data structure.
ulReserved (ULONG) - return
Zero. Reserved value.

Returns

ulReserved (ULONG) - return
Zero. Reserved value.

Remarks

The format of the data structure pointed to by MsgParam2 is defined by devices that return this message.

Unlike most media control interface notification messages, **MM_MCIEVENT** is **sent** (rather than posted) to the application's message queue. The data structure pointed to by the message parameter is considered valid only during processing of the message.

Default Processing

The default window procedure does not expect to receive this message and therefore takes no action on it, other than to set rc to the default value of FALSE.