Share via

TPM_QUERY_THREAD_COUNT

  • Article

This message is sent once to the TestProc function to query the default number of threads that are to be created to execute the test.

Parameters

  • uMsg
    TPM_QUERY_THREAD_COUNT message.
  • tpParam
    Pointer to a TPS_QUERY_THREAD_COUNT structure.
  • dwThreadCount
    The default number of threads requested by this test case for running. A value of 0 indicates that Tux Client will run the test on its main process thread. A value of 1 indicates that a single thread will be created and the test will run on it while Tux's main thread waits for it to complete. This can be useful for testing interfaces, such as GDI, that behave differently when not running on the main thread of a process. A thread value greater than 1 will cause that number of threads to get created and run the test in parallel. In this case, Tux will create n threads, wait for them to become alive and idle, and then simultaneously release them to run the test case. Tux's main thread will wait until all the threads have completed and then return a single result.

Return Values

Return TPR_HANDLED to set the default number of threads to the value specified in the dwThreadCount field of the TPS_QUERY_TREAD_COUNT structure. Return TPR_NOT_HANDLED to use the default number of threads.

Remarks

The default thread count for each function is 0, which indicates that the test on Tux's main thread should be executed. If a value other than the default is desired, the test case should set the dwThreadCount parameter to the desired value and return TPR_HANDLED.

Requirements

OS Versions: Windows CE 3.0 and later.
Header: Tux.h.

See Also

TestProc | TPS_QUERY_THREAD_COUNT | Tux Architecture

 Last updated on Friday, October 08, 2004

© 1992-2003 Microsoft Corporation. All rights reserved.