Main Loop Hooks/zh CN: what changed
Revision 2 to 3. Removed lines have a minus sign; added lines have a plus sign.
| Old | New | Line | |
|---|---|---|---|
| 1 | 1 | ## 问题陈述 | |
| 2 | 2 | ||
| 3 | 3 | 当你需要等待一些事件（如：socket、pipe...）的触发，在不阻塞主线程（main thread GUI）显示而又不使用多线程方式，反馈到主线程时。解决方法是把事件监视挂接（handles）到主事件循环中。 | |
| 4 | 4 | ||
| 5 | 5 | ## 结决的详细内容 | |
| 6 | 6 | ||
| 7 | 7 | 在单元文件 [[doc:lcl/lclintf|LCLIntf]] 中 2 个函数用来实现这个功能，如下： | |
| 8 | 8 | ||
| 9 | - | ||
| 10 | - | ||
| 11 | - | ||
| 12 | - | ||
| 9 | + | ``` pascal | |
| 10 | + | AddEventHandler(AHandle: THandle; AFlags: dword; | |
| 11 | + | AEventHandler: TWaitHandleEvent; AData: PtrInt): PEventHandler; | |
| 12 | + | RemoveEventHandler(var AHandler: PEventHandler); | |
| 13 | + | SetEventHandlerFlags(AHandler: PEventHandler; NewFlags: dword); | |
| 14 | + | ``` | |
| 13 | 15 | ||
| 14 | 16 | 类[[doc:lcl/interfacebase/twaithandleevent.html|TWaitHandleEvent]] 定义于 单元文件 InterfaceBase 其定义如下: | |
| 15 | 17 | ||
| 16 | - | ||
| 18 | + | ``` pascal | |
| 19 | + | TWaitHandleEvent = procedure(AData: PtrInt; AFlags: dword) of object; | |
| 20 | + | ``` | |
| 17 | 21 | ||
| 18 | 22 | [[doc:lcl/lclintf/addeventhandler.html|AddEventHandler]] 在主事件循环中添加一个事件监视挂接，当挂接被触发，作为 AData 参数传入的回调函数 ACallback 被调用，并传回相应的标志 Flags 信息，包含操作系统指定的信息。回传标志 Flags 到 AddEventHandler 中可以用 SetEventHandlerFlags 修改。使用 AddEventHandler 返回的挂接指针 PEventHandler 被 RemoveEventHandler 用于停止此挂接监视。 | |
| 19 | 23 | ||
| 20 | 24 | [[doc:lcl/lclintf/removeeventhandler.html|RemoveEventHandler]] 停止指定的挂接监视。RemoveEventHandler 将把之前返回的 AHandler 设为nil， 此变量参数是 AddEventHandler 返回的指针（pointer）。 | |
| 21 | 25 | ||
| 22 | 26 | ### Windows | |
| 23 | 27 | ||
| 24 | 28 | 在当前的实现中，AddEventHandler 里的 AFlags 参数未被使用， 在 TWaitHandleEvent 中 AFlags 被赋值为 0。 | |
| 25 | 29 | ||
| 26 | 30 | Win32 支持以下的挂接监视类型, 基本上都被 MsgWaitForMultipleObjects 所支持: | |
| 27 | 31 | ||
| 28 | 32 | - change notifications (针对文件和文件夹) | |
| 29 | 33 | - console input （控制台输入） | |
| 30 | 34 | - events: signalled with SetEvent winapi function | |
| 31 | 35 | - mutexes: signalled when it is not owned anymore | |
| 32 | 36 | - processes: signalled when they terminate | |
| 33 | 37 | - semaphore: signalled when it's *count* is greater than zero | |
| 34 | 38 | - threads: signalled when they terminate | |
| 35 | 39 | - timers: signalled when expired, see SetWaitableTimer | |
| 36 | 40 | ||
| 37 | 41 | ### Gtk/Unix | |
| 38 | 42 | ||
| 39 | 43 | The AFlags parameter in AddEventHandler specifies the condition in which the handle should be signalled, with the possible values being the ones documented in the GIOCondition type in the [glib](http://developer.gimp.org/api/2.0/glib/glib-IO-Channels.html#GIOCondition) reference. | |
| 40 | 44 | ||
| 41 | 45 | In the callback, the AFlags will contain the condition, of the above referenced GIOCondition type, that was satisfied. | |
| 42 | 46 | ||
| 43 | 47 | Gtk/unix supports the following handle types: | |
| 44 | 48 | ||
| 45 | 49 | - files | |
| 46 | 50 | - sockets | |
| 47 | 51 | - pipes | |
| 48 | 52 | ||
| 49 | 53 | Note that win32 does not support sockets or pipes (at least, their use is "discouraged" by MSDN). Suggestion: use WSAEventSelect to create an event associated with a socket and pass the event handle. | |
| 50 | 54 | ||
| 51 | 55 | ### Pipes 和 Process 的终止 | |
| 52 | 56 | ||
| 53 | 57 | 由于要提供交叉平台的解决方法针对 Pipes（Win32 不支持） 和 Process（gtk/unix 不支持），所附加的函数如下： | |
| 54 | 58 | ||
| 55 | - | ||
| 56 | - | ||
| 57 | - | ||
| 59 | + | ``` pascal | |
| 60 | + | TChildExitReason = (cerExit, cerSignal); | |
| 61 | + | TPipeReason = (prDataAvailable, prBroken, prCanWrite); | |
| 62 | + | TPipeReasons = set of TPipeReason; | |
| 58 | 63 | ||
| 59 | - | ||
| 60 | - | ||
| 64 | + | TChildExitEvent = procedure(AData: PtrInt; AReason: TChildExitReason; AInfo: dword) of object; | |
| 65 | + | TPipeEvent = procedure(AData: PtrInt; AReasons: TPipeReasons) of object; | |
| 66 | + | ``` | |
| 61 | 67 | ||
| 62 | - | ||
| 63 | - | ||
| 64 | - | ||
| 68 | + | ``` pascal | |
| 69 | + | function AddProcessEventHandler(AHandle: THandle; | |
| 70 | + | AEventHandler: TChildExitEvent; AData: PtrInt): PProcessEventHandler; | |
| 71 | + | procedure RemoveProcessEventHandler(var AHandler: PProcessEventHandler); | |
| 65 | 72 | ||
| 66 | - | ||
| 67 | - | ||
| 68 | - | ||
| 73 | + | function AddPipeEventHandler(AHandle: THandle; | |
| 74 | + | AEventHandler: TPipeEvent; AData: PtrInt): PPipeEventHandler; | |
| 75 | + | procedure RemovePipeEventHandler(var AHandler: PPipeEventHandler); | |
| 76 | + | ``` | |
| 69 | 77 | ||
| 70 | 78 | When a process terminates the event handler specified will be called. AInfo will contain the exit code if AReason is cerExit, or (on unix only) the termination signal if AReason is cerSignal. For gtk/unix, use the PID to watch as AHandle. Internally, a signal handler is installed to catch the SIGCHLD signal. On win32, AddEventHandler is used to watch process termination. | |
| 71 | 79 | ||
| 72 | 80 | To watch a pipe for incoming data, pass the file descriptor (unix) or the pipe read-end handle to AddPipeEventHandler with a custom chosen event handler method as AEventHandler. On gtk/unix, AddEventHandler is called to watch the file descriptor for traffic. On win32, the message loop will timeout every 100 msecs to check all watched pipes for available data; if data is available, the event handler is called. | |
| 73 | 81 | ||
| 74 | 82 | --- | |
| 75 | 83 | *From the Free Pascal wiki, page "Main Loop Hooks/zh CN", as it stood on 2011-02-01 after a change by Chronos, out of the wiki's dump of 2024-05-26. Copyright stays with the author who wrote it, according to the old wiki's [[Licensing]] page. If you have concerns about this material, [message the admin](/wiki-contact).* |