IBtm::Environment() method information

M&M FDT 1.2.1 Online Specification
IBtm::Environment() method information

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

4.7.1.2 IBtm::Environment()

This method can be called in the states:

HRESULT Environment (
[in] BSTR systemTag,
[in] IFdtContainer* container,
[out, retval] VARIANT_BOOL* result
);

Description:

For description of this method refer to the method IDtm::Environment().

Parameters:

systemTag
container

Return Value:

result

TRUE DTM has accepted the data FALSE The operation failed.

Behavior:

Comments:

-/-

Comments from fdtFAQ Forum:

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

The specification says "The DTM should not store the systemTag to prevent side effect ...". The intension probably is that the DTM should not rely on that information, because it may change. In fact, the DTM should also not rely on the system tags of the children it has. The DTM must be able to identify the child DTMs another way (e.g. address, flags). However, for performance reasons, you might want to implement e.g. an address cache, which in fact stores the system tags as well. The frame application may change the system tag of a DTM at any startup, if it likes to do so. Also the system tags of the children may change at any time. The DTM could detect this by storing its own system tag and comparing it to the old one. If the DTMs system tag has changed, the DTM must be prepared that the children system tags also changed. This may happen in two situations: a) The frame application changes the system tag at any time. b) The frame application has just imported or copied the DTM and therefore needed to specify a new system tag.

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