Bluetooth Special Interest Group Inc. BTSIG15A Manual De Usuario
Printed Documentation
66
The custom Implicit Send DLL will be used starting with the next test case that is executed in the project.
Usage Notes
•
The custom Implicit Send DLL may be disabled at any time by returning to the Project Settings page and
removing the checkmark from the box labeled “Use”.
removing the checkmark from the box labeled “Use”.
•
The procedure above attaches a custom DLL to one and only project in a single workspace. The process must
be repeated to use the DLL with other projects in the same workspace, or, with the same test suite (project) in a
different workspace.
be repeated to use the DLL with other projects in the same workspace, or, with the same test suite (project) in a
different workspace.
Technical Tidbits
Automatic dismissal of Implicit Send requests
At various points during the execution of a test, the test case implementation can detect that an action requested via
Implicit Send has occurred. When this happens, the test case may attempt to complete the ImplicitSendStyle() or
ImplicitSendPinCode() operation that is in progress.
Implicit Send has occurred. When this happens, the test case may attempt to complete the ImplicitSendStyle() or
ImplicitSendPinCode() operation that is in progress.
This most commonly occurs with messages using MMI_Style_Ok_Cancel2. These messages tend to be “transient”, for
example, “Using the IUT, make a connection to the PTS”. For these types of actions, there is no need to require operator
interaction with PTS. The operator can simply take whatever steps are necessary on the IUT to cause the connection to
happen; the test case can then detect the connection and take down the dialog.
example, “Using the IUT, make a connection to the PTS”. For these types of actions, there is no need to require operator
interaction with PTS. The operator can simply take whatever steps are necessary on the IUT to cause the connection to
happen; the test case can then detect the connection and take down the dialog.
The mechanism used to do this is to send simulated button presses to a dialog whose title is “User Action Required”. This
works very well with the default Implicit Send DLL because all of the dialogs it displays are titled “User Action Required”.
works very well with the default Implicit Send DLL because all of the dialogs it displays are titled “User Action Required”.
This however may not work very well with custom Implicit Send DLLs – especially ones that have no need to create popup
dialogs. The test case will send the simulated button presses, but no one – most specifically the functions in the custom
DLL – will be listening.
dialogs. The test case will send the simulated button presses, but no one – most specifically the functions in the custom
DLL – will be listening.
This situation may not be as bad as it seems. In all likelihood the IUT also knows that the requested action has taken
place and would normally notify the user of the device. When the user of the device is replaced with an automation test
platform, the platform can detect the situation and notify the custom Implicit Send DLL.
place and would normally notify the user of the device. When the user of the device is replaced with an automation test
platform, the platform can detect the situation and notify the custom Implicit Send DLL.
If it turns out that a custom DLL needs to know when the simulated button presses occur, it could create a hidden window
whose title is “User Action Requested”. This would allow the delivery of the simulated button presses to the custom
Implicit Send DLL.
whose title is “User Action Requested”. This would allow the delivery of the simulated button presses to the custom
Implicit Send DLL.