|
M&M FDT 1.2.1 Online Specification |
Interfaces and Methods - Schemas - FDT Specification - Quicklinks - Abbreviations
IFdtActiveX2
CloseChannelActiveXControlRequest
OpenChannelActiveXControlRequest
OpenDialogActiveXControlRequest
OpenDialogChannelActiveXControlRequest
4.9.6.1 IFdtActiveX2::OpenDialogActiveXControlRequest()
| This method can be called in the states: |       |
|
HRESULT OpenDialogActiveXControlRequest ( [in] BSTR systemTag, [in] FdtXmlDocument functionCall, [out, retval] VARIANT_BOOL* result ); |
Description:
| Request to open ActiveX control for a certain DTM in a modal dialog of Frame Application. |
Parameters:
| systemTag | Identifier of the device instance |
| functionCall | XML document containing the DTM specific function id for the requested user interface specified by the DTMFunctionCallSchema |
Return Value:
| result | TRUE The requested ActiveX control was instantiated by the Frame Application FALSE The operation failed (i.e. because Frame Application is running without user interface). |
Behavior:
| This method is used to open an ActiveX user interface, which must be instantiated and embedded in a modal dialog by the Frame Application. The Frame Application will establish the link between the new user interface and the DTM via IDtmActiveXControl::Init(). This method behaves always modal. Frame Application at least has to ensure that all ActiveX controls of calling DTM are disabled; no further user input is possible. The opened ActiveX user interface must call IFdtActiveX:CloseActiveXControlRequest() if it wants to be closed later. OpenDialogActiveXControlRequest() works synchronously so that the DTM is block until ActiveX user interface and corresponding dialog are closed. |
Comments:
| A DTM always should use this method for more complex dialogs rather than calling IFdtDialog::UserDialog() with FDTUserMessageSchema XML containing variables to edit, because this is not supported by almost all Frame Applications. Call of IFdtDialog::UserDialog() should be preferred if FDTUserMessage XML only contains text lines. Caller of OpenDialogActiveXControlRequest() have to be aware of some synchronization circumstances which arise if modal dialogs are opened. FDT 1.2 Addendum specification discusses this topic for IFdtDialog::UserDialog() and IDtmEvents:OnErrorMessage() calls (refer FDT Best Practices – A closer look at message loops). |
© by M&M Software GmbH, parts of this website taken from FDT Interface Specification Version 1.2.1, © by FDT Group, AISBL.
This website is published for support of M&M products as granted in license conditions, chapter 2.1.
Last updated 2015-02-05 15:17
Email: FDT Technical Support Line.