Type a page name and press Enter. You'll jump to the page if it exists, or you can create it if it doesn't.
To create a page in a module other than kernel32, prefix the name with the module name and a period.
/// By default, the callback function is queued to a non-I/O worker thread.
WT_EXECUTEDEFAULT = 0x00000000,
/// The callback function is invoked by the timer thread itself. This flag should be used only for short tasks or it could affect other timer operations.
/// The callback function is queued as an APC. It should not perform alertable wait operations.
WT_EXECUTEINTIMERTHREAD = 0x00000020,
/// The callback function is queued to an I/O worker thread. This flag should be used if the function should be executed in a thread that waits in an alertable state.
/// The callback function is queued as an APC. Be sure to address reentrancy issues if the function performs an alertable wait operation.
WT_EXECUTEINIOTHREAD = 0x00000001,
/// The callback function is queued to a thread that never terminates. It does not guarantee that the same thread is used each time. This flag should be used only for short tasks or it could affect other timer operations.
/// Note that currently no worker thread is truly persistent, although no worker thread will terminate if there are any pending I/O requests.
WT_EXECUTEINPERSISTENTTHREAD = 0x00000080,
/// The callback function can perform a long wait. This flag helps the system to decide if it should create a new thread.
WT_EXECUTELONGFUNCTION = 0x00000010,
/// The timer will be set to the signaled state only once. If this flag is set, the Period parameter must be zero.
WT_EXECUTEONLYONCE = 0x00000008,
/// Callback functions will use the current access token, whether it is a process or impersonation token. If this flag is not specified, callback functions execute only with the process token.
/// Windows XP/2000: This flag is not supported until Windows XP with SP2 and Windows Server 2003.
WT_TRANSFER_IMPERSONATION = 0x00000100
An IntPtr is a pointer to a memory location (unmanaged) that adapts to the platform it is running on (64-bit, etc.) UNLIKE a standard int/Integer. You should always use this type for unmanaged calls that require it, even though an int will appear to work on your development machine.
1/13/2008 4:00:13 AM - Damon Carr-18.104.22.168
Please edit this page!
Do you have...
helpful tips or sample code to share for using this API in managed code?
corrections to the existing content?
variations of the signature you want to share?
additional languages you want to include?
Select "Edit This Page" on the right hand toolbar and edit it! Or add new pages containing supporting types needed for this API (structures, delegates, and more).