|
M&M FDT 1.2.1 Online Specification |
Interfaces and Methods - Schemas - FDT Specification - Quicklinks - Abbreviations
4.5.2.1 IFdtChannelActiveXInformation::GetChannelActiveXGuid()
| This method can be called in the states: |       |
|
HRESULT GetChannelActiveXGuid ( [in] FdtXmlDocument functionCall, [out, retval] FdtUUIDString* result ); |
Description:
| Returns the UUID for the ActiveX control according to the function call. |
Parameters:
| functionCall | XML document containing the function id for the requested user interface specified by the DTMFunctionCallSchema |
Return Value:
| result | UUID for an ActiveX control |
Behavior:
| Returns a UUID that the Frame Application can use to instantiate the control. If a requested function is not supported the method returns NULL pointer For a communication channel, it would be the user interface to set communication specific parameters. |
Comments:
| -/- |
Comments from fdtFAQ Forum:
| Thomas Weller created on 2006-06-23, last updated on 2006-06-23 |
| The original declaration obviously misses the name of the parameter which is 'functionCall'. This has been corrected here. |
| Thomas Weller created on 2006-11-10, last updated on 2006-11-10 |
| Please not that InvokeFunctionRequest() and StartApplication() are not available at a channel. Therefore all functions of a channel result in ActiveX controls. That's also why there is no hasGUI attribute in the DTMChannelFunctionsSchema. |
| Thomas Weller created on 2006-11-10, last updated on 2006-11-10 |
| See IDtmActiveXInformation::GetActiveXProgId() for an important hint on the use of <ApplicationID>. |
© 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.