Default constructor.

Ensures that the attached scheduler loop, and all nested loops, are stopped prior to destruction.

AsyncStop()

Stops the scheduling loop owned by this object.

Note that the corresponding call to Start() only returns once all nested scheduler loops have stopped.

Stops the scheduling loop owned by this object, specifying a callback.

This version of AsyncStop() provides a callback which is invoked immediately after the scheduler loop actually stops before the corresponding call to Start() returns.

Note that the corresponding call to Start() only returns once all nested scheduler loops have stopped.

Reports whether stopping will have immediate effect.

This returns an indication of whether a call to AsyncStop() would be expected to stop the scheduler loop immediately, or whether it will have to wait until nested scheduler loops have stopped. This may alter which version of AsyncStop() you would want to call.

Reports whether this CActiveSchedulerWait object is currently started.

Note: a CActiveSchedulerWait object itself becomes "stopped" as soon as AsyncStop() is called, and can be started again immediately if required (but this would start a new nested level of the scheduler).

CActiveSchedulerWait::Start CActiveSchedulerWait::AsyncStop

Starts a new wait loop under the control of the current active scheduler.

Compared with CActiveScheduler::Start(), this object owns control of the scheduling loop that is started, and that loop can only be stopped by using this objects AsyncStop() function or the CActiveScheduler::Halt() function. Start() only returns when either of thos has occurred.

This is the preferred way to start a nested wait loop. Typically, a nested wait loop is used when the handling of a completed event in an active object requires processing further events from the other active objects before it can complete. This is a form of modal processing.