圣母百花大教堂怎么过:求助:帮忙翻译一段有关计算机专业的英文

来源:百度文库 编辑:高校问答 时间:2024/05/05 05:54:26
DAT_EVENT Handling Errors
One of the most common problems between a data source and application is the management of DG_CONTROL / DAT_EVENT / MSG_PROCESSEVENT. The symptoms are not immediately obvious, so it is worth mentioning them to assist new developers in quickly
identifying and solving the problem.
Cannot use TAB or Keyboard Shortcuts to Navigate TWAIN Dialog
The cause of this can be one of two things. Either the application is not forwarding all messages to TWAIN through the DAT_EVENT mechanism, or the data source is not properly processing the DAT_EVENT messages. (Windows: calling IsDialogMessage for each forwarded message with TWAIN Dialog handle) TWAIN Dialog Box Combo Boxes cannot be opened, Edit boxes produce multiple chars per keystroke This case is caused by processing TWAIN Dialog Messages twice. Either the data
source has not returned the proper return code in response to DAT_EVENT calls (Windows: TWRC_DSEVENT when IsDialogMessage returns TRUE), or the application is ignoring the return code.
This is not a problem when data source operates through TWAIN Thunker Problems with the application handling of these messages are not often detected if the data source is operating through the TWAIN Thunking mechanism. This is because the Thunker process has a separate Window and Message pump that properly dispatch DAT_EVENT messages to the data source. Any mistake in application handling will pass without notice since all DAT_EVENT calls will return TWRC_NOTDSEVENT.
(with the exception of important messages such as MSG_XFERREADY.)
Problem seems erratic, keyboard shortcuts and Tab key work for Message Boxes, but not TWAIN Dialog This observation often further confuses the issue. In Windows, a standard Message box
is Modal, and operates from a local message pump until the user closes it. All messages are properly dispatched to the message box since it does not rely on the application message pump. The TWAIN Dialog is slightly different since it is
implemented Modeless. There is no easy way to duplicate Modal behavior for the TWAIN Dialog.

处理
共同的问题的错误一的DAT_EVENT在数据来源和应用之间是DG_CONTROL的管理/ DAT_EVENT/ MSG_PROCESSEVENT. 症状不立刻是显然的, 如此它在快辩认和解决问题值得提及
他们协助新的开发商。
不能使用制表符或驾驶吐温对话的键盘快捷键
此的起因可以是二件事之一。 任一应用不是向前所有消息对吐温通过DAT_EVENT机制, ou a origem dos dados não está processando corretamente as mensagens de DAT_EVENT. (窗口: 不可能打开叫IsDialogMessage为每则顺向讯息用吐温对话把柄)吐温对话箱组合框, 校正框产物多炭灰每个这个案件是由两次处理吐温对话消息造成的击键。 或者
数据源未退回适当的返回码以回应DAT_EVENT电话(窗口: TWRC_DSEVENT,当IsDialogMessage退回真实), 或应用忽略返回码。
这不是问题,当数据来源通过吐温时经营问题以应用处理这些消息经常没有被查出的Thunker数据来源是否通过吐温Thunking机制经营。 这是,因为Thunker过程有适当地派遣DAT_EVENT消息到数据来源的一个分开的窗口和消息泵浦。 所有差错在应用处理不预先通知将通过,因为所有DAT_EVENT电话将退回TWRC_NOTDSEVENT。
(除重要消息之外例如MSG_XFERREADY。)
问题似乎古怪, 键盘快捷键和标记键为信息框运作, 但不是吐温对话这观察经常更加进一步混淆问题。 在窗口, 一个标准信息框
是语气的, 并且从一个地方消息泵浦操作,直到用户关闭它。 因为它不依靠应用消息泵浦,所有消息适当地被派遣到信息框。 因为它是被实施的非模态的,吐温对话是
轻微地不同的。 没有容易的方法复制语气行为为吐温对话。