要求完成功能如下:函数A:处理某些过程,等待用户响应指令判断十分继续function aa:string;
begin
事件A
事件B 发生事件B时候询问调用本函数的使用者使用继续,否则中断
。。
等待;
事件C
end;procedure TForm1.Button1Click(Sender: TObject);
var
begin
调用函数aa 当出现事件B时弹出对话框并决定aa函数是否继续
if application.MessageBox('是否继续?','提示',MB_OKCANCEL)=IDok then
end;
请问有谁知道?
begin
事件A
事件B 发生事件B时候询问调用本函数的使用者使用继续,否则中断
。。
等待;
事件C
end;procedure TForm1.Button1Click(Sender: TObject);
var
begin
调用函数aa 当出现事件B时弹出对话框并决定aa函数是否继续
if application.MessageBox('是否继续?','提示',MB_OKCANCEL)=IDok then
end;
请问有谁知道?
解决方案 »
- delphi checklistbox问题
- Edit赋值问题的变化
- installshield与ODBC的问题?
- 还是fastreport的问题,请问如何实现
- 加密狗的外壳加密程序,能否对数据库进行加密? (SQL)
- 各位大哥,如何让qreport中的qrdbtext的值自动折行阿
- 请问一个关于生成无边框窗体的问题?
- 急!!!为何adotable1[j]中不能用参数j???
- 怎么用OLE实现与手机的通讯??
- 简单问题,怎么样创建一个总是浮在另一个Form上的Form
- 怎样可以实现vclskin皮肤更新,我想在程序里控制它.可以吗 ?
- delphi数组索引是从1到最大值,而在引用Form上的控件时候,索
DWORD nCount, // number of handles in the handle array
CONST HANDLE *lpHandles, // pointer to the object-handle array
BOOL fWaitAll, // wait flag
DWORD dwMilliseconds // time-out interval in milliseconds
);
用这个API函数应该可以实现你的要求。
使用也很简单,DWORD nCount是需要等待的对象个数,CONST HANDLE *lpHandles对象句柄数组,
BOOL fWaitAll,是否等全部对象发信号,还是等任意一个发信号, DWORD dwMilliseconds表示等待超时的时间千分之一秒。
根据它的返回值来判断,倒底发生了什么事。
它一般用于,有信号状态的对象
原文如下:
The WaitForMultipleObjects function can specify handles of any of the following object types in the lpHandles array: Change notification
Console input
Event
Job
Mutex
Process
Semaphore
Thread
Waitable timer
The WaitForMultipleObjects function returns when one of the following occurs: Either any one or all of the specified objects are in the signaled state.
The time-out interval elapses.
DWORD WaitForMultipleObjects(
DWORD nCount, // number of handles in the handle array
CONST HANDLE *lpHandles, // pointer to the object-handle array
BOOL fWaitAll, // wait flag
DWORD dwMilliseconds // time-out interval in milliseconds
);
Parameters
nCount
Specifies the number of object handles in the array pointed to by lpHandles. The maximum number of object handles is MAXIMUM_WAIT_OBJECTS.
lpHandles
Pointer to an array of object handles. For a list of the object types whose handles can be specified, see the following Res section. The array can contain handles of objects of different types.
Windows NT: The handles must have SYNCHRONIZE access. For more information, see Standard Access Rights. Windows 95: No handle may be a duplicate of another handle created using DuplicateHandle. fWaitAll
Specifies the wait type. If TRUE, the function returns when the state all objects in the lpHandles array is signaled. If FALSE, the function returns when the state of any one of the objects set to is signaled. In the latter case, the return value indicates the object whose state caused the function to return.
dwMilliseconds
Specifies the time-out interval, in milliseconds. The function returns if the interval elapses, even if the conditions specified by the bWaitAll parameter are not met. If dwMilliseconds is zero, the function tests the states of the specified objects and returns immediately. If dwMilliseconds is INFINITE, the function's time-out interval never elapses.
Return Values
If the function succeeds, the return value indicates the event that caused the function to return. This value can be one of the following. Value Meaning
WAIT_OBJECT_0 to (WAIT_OBJECT_0 + nCount – 1) If bWaitAll is TRUE, the return value indicates that the state of all specified objects is signaled.
If bWaitAll is FALSE, the return value minus WAIT_OBJECT_0 indicates the lpHandles array index of the object that satisfied the wait. If more than one object became signalled during the call, this is the array index of the signalled object with the smallest index value of all the signalled objects.
WAIT_ABANDONED_0 to (WAIT_ABANDONED_0 + nCount – 1) If bWaitAll is TRUE, the return value indicates that the state of all specified objects is signaled and at least one of the objects is an abandoned mutex object.
If bWaitAll is FALSE, the return value minus WAIT_ABANDONED_0 indicates the lpHandles array index of an abandoned mutex object that satisfied the wait.
WAIT_TIMEOUT The time-out interval elapsed and the conditions specified by the bWaitAll parameter are not satisfied.
If the function fails, the return value is WAIT_FAILED. To get extended error information, call GetLastError. Res
The WaitForMultipleObjects function determines whether the wait criteria have been met. If the criteria have not been met, the calling thread enters an efficient wait state, consuming very little processor time while waiting for the criteria to be met.When fWaitAll is TRUE, the function's wait operation is completed only when the states of all objects have been set to signaled. The function does not modify the states of the specified objects until the states of all objects have been set to signaled. For example, a mutex can be signaled, but the thread does not get ownership until the states of the other objects are also set to signaled. In the meantime, some other thread may get ownership of the mutex, thereby setting its state to nonsignaled.Before returning, a wait function modifies the state of some types of synchronization objects. Modification occurs only for the object or objects whose signaled state caused the function to return. For example, the count of a semaphore object is decreased by one. When fWaitAll is FALSE, and multiple objects are in the signaled state, the function chooses one of the objects to satisfy the wait; the states of the objects not selected are unaffected. The WaitForMultipleObjects function can specify handles of any of the following object types in the lpHandles array: Change notification
Console input
Event
Job
Mutex
Process
Semaphore
Thread
Waitable timer
For more information, see Synchronization Objects.Use caution when calling the wait functions and code that directly or indirectly creates windows. If a thread creates any windows, it must process messages. Message broadcasts are sent to all windows in the system. A thread that uses a wait function with no time-out interval may cause the system to become deadlocked. Two examples of code that indirectly creates windows are DDE and COM CoInitialize. Therefore, if you have a thread that creates windows, use MsgWaitForMultipleObjects or MsgWaitForMultipleObjectsEx, rather than WaitForMultipleObjects.Windows CE: Windows CE does not support waiting for semaphores, change notification objects, console input, and timers.QuickInfo
Windows NT: Requires version 3.1 or later.
Windows: Requires Windows 95 or later.
Windows CE: Requires version 1.0 or later.
Header: Declared in winbase.h.
Import Library: Use kernel32.lib.See Also
Synchronization Overview, Synchronization Functions, CancelWaitableTimer, CreateEvent, CreateFile, CreateMutex, CreateProcess, CreateRemoteThread, CreateSemaphore, CreateThread, CreateWaitableTimer, FindFirstChangeNotification, GetStdHandle, MsgWaitForMultipleObjects, MsgWaitForMultipleObjectsEx, OpenEvent, OpenMutex, OpenProcess, OpenSemaphore, OpenWaitableTimer, PulseEvent, QueueUserAPC, ResetEvent, SetEvent, SetWaitableTimer