|
M&M FDT 1.2.1 Online Specification |
Interfaces and Methods - Schemas - FDT Specification - Quicklinks - Abbreviations
4.3.4.1 IDtmApplication::ExitApplication()
| This method can be called in the states: |      |
|
HRESULT ExitApplication ( [in] FdtUUIDString invokeId, [out, retval] VARIANT_BOOL* result ); |
Description:
| Notification to a DTM to close an user interfaces identified by the invoke id. |
Parameters:
| invokeId | Identifier for the started application. Same value as provided in the corresponding call of IDtmApplication::StartApplication() |
Return Value:
| result | TRUE The specified application will be closed FALSE The operation failed. |
Behavior:
| This method works asynchronous. That means that the DTM just checks whether it can close the user interfaces or not. In case it can, it first returns TRUE and then starts its shut down procedure for the user interface. During this shut down it has to unlock its instance data set and release the online connection to its device if necessary. Finally, it has to notify the Frame Application via IDtmEvents::OnApplicationClosed(). This notification will cause the related releases on Frame Application’s side. The DTM itself is not terminated. In case of errors, the DTM should supply further details via IDtmEvents::OnErrorMessage(). The invoke id is used by a Frame Application for the association at the callback interface if the application is terminated. (see IDtmEvents::OnApplicationClosed()). |
Comments:
| This method has to work asynchronous, because a synchronous call may block the Frame Application interfaces. |
© 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.