Jump to content

WM TIMER

From EDM2
Revision as of 23:35, 13 April 2025 by Martini (talk | contribs) (Created page with "This message is posted when a timer times out. ==Syntax== <pre> param1 USHORT idTimer; Timer identity.: param2 ULONG ulReserved; Reserved value, should be 0.: </pre> ==Parameters== ;''idTimer'' (USHORT) - input: Timer identity. :Any timer Ids that are not being used must be passed on the default window procedure. ;''ulReserved'' (ULONG) - input: Reserved value, should be 0. ==Returns== ;''ulReserved'' (ULONG) - returns: Reserved value, should...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This message is posted when a timer times out.

Syntax

param1
    USHORT  idTimer;    /* Timer identity. */

param2
    ULONG   ulReserved; /* Reserved value, should be 0. */

Parameters

idTimer (USHORT) - input
Timer identity.
Any timer Ids that are not being used must be passed on the default window procedure.
ulReserved (ULONG) - input
Reserved value, should be 0.

Returns

ulReserved (ULONG) - returns
Reserved value, should be 0.

Remarks

This message is always queued and is processed specially by the WinGetMsg and WinPeekMsg calls, as follows:

  1. Timers are processed only by the WinGetMsg and WinPeekMsg calls.
  2. A timer posts only one WM_TIMER message at a time.
  3. WM_TIMER messages are queued lower than all other messages except WM_SEM4 messages.

Default Processing

The default window procedure takes no action on this message, other than to set ulReserved to 0.