IDtm::PrivateDialogEnabled() method information

M&M FDT 1.2.1 Online Specification
IDtm::PrivateDialogEnabled() method information

Interfaces and Methods - Schemas - FDT Specification - Quicklinks - Abbreviations

4.3.1.9 IDtm::PrivateDialogEnabled()

This method can be called in the states:

HRESULT PrivateDialogEnabled (
[in] VARIANT_BOOL enabled,
[out, retval] VARIANT_BOOL* result
);

Description:

Sends a notification to a DTM whether it is allowed to open a private dialog window.

Parameters:

enabled

TRUE means that it is allowed for a DTM to open a dialog window

Return Value:

result

TRUE The function succeeded. FALSE The function failed.

Behavior:

This special state is set by a Frame Application during runtime. This may be necessary if currently a user action must no be disturbed or if it is not allowed, that a dynamically opened window gets the focus or hides other windows. Enabled set to FALSE mean that the DTM must not open any dialog windows. If at this state any error occurs the DTM can send a notification to the Frame Application via IDtmEvents::OnErrorMessage(). If the DTM needs a user action, and therefore has to open a user dialog, it should first ask the Frame Application via the IFdtDialog interface. At this request the default response is not to open the dialog. So it is up to the Frame Application to allow opening the dialog, delay the request until the current user action is finished, or to refuse the request by sending the default response. If a DTM uses ActiveX controls as user interfaces, the DTM has to inform its open controls whether they are allowed to open dialog windows.

Comments:

-/-

Related dtmINSPECTOR hints:

Thomas Weller
created on 2006-12-05, last updated on 2006-12-05

The DTM may only reject this call in case the method is called in wrong state. In all other cases the DTM must be able to prevent private dialogs.

Comments from fdtFAQ Forum:

Thomas Weller
created on 2008-01-29, last updated on 2013-09-25

Private dialogs will be shown on the machine where the private dialog is invoked. In theory, the DTM and ActiveX could run on different machines if the ActiveX opens the private dialog. If the DTM opens a private dialog on behalf of the ActiveX, this might be on a different machine. Best is to not open private dialogs by the DTM at all.

Thomas Weller
created on 2013-09-25, last updated on 2013-09-25

For a definition of what exactly a private dialog is, see the best practice document 0003-0009-000.

© 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.