|
M&M FDT 1.2.1 Online Specification |
Interfaces and Methods - Schemas - FDT Specification - Quicklinks - Abbreviations
4.9.7.2 IFdtBulkData::GetProjectRelatedPath()
| This method can be called in the states: |        |
|
HRESULT GetProjectRelatedPath ( [in] BSTR systemTag, [out, retval] BSTR* result ); |
Description:
| Returns the project related path for bulk data. Returns a unique file system path (directory) for any combination of project and DTM type (e.g. it returns different paths for the same DTM type within two projects). |
Parameters:
| systemTag | Identifier of the device instance |
Return Value:
| result | Project related path (directory) for bulk data including a trailing backslash |
Behavior:
| The Frame Application offers a DTM a way to request a project specific path to an area which could be used to store data in a DTM specific way. It is up to a DTM to decide in which way the data will be stored. It could be a binary format by using IStorage or PropertyBag or even an ASCII-File. The Frame Application is responsible to provide an unique path for each DTM type within a project. It must be an absolute path to allow a DTM the direct access. |
Comments:
| A DTM must work without any side effects if a path is not available. If the DTM holds any references between project and instance related data it must clean up these data if IDtm::PrepareToDelete() is called. There is no FDT specific locking mechanism, so the DTM is responsible for consistence data. |
© 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.