 | M&M FDT 1.2.1 Online Specification |
Interfaces and Methods - Schemas - FDT Specification - Quicklinks - Abbreviations
7.1 FDT Registry and Device Information
7.1.1 Visibility of business objects of a DTM
7.1.2 Component Categories
7.1.3 Registry Entries
7.1.4 Installation Issues
7.1.5 Microsoft’s Standard Component Categories Manager
7.1.6 Building a Frame Application-Database of Supported Devices
7.1.7 DTM Registration
7.1.1 Visibility of business objects of a DTM
Each business object class within a DTM which should be visible for integration within the Frame Application, or a separate DTM presentation object must be registered in the Windows Registry using FDT-specific COM-component category entries. These class objects of a DTM can than be detected by a Frame Application or a configuration tool using the Microsoft standard component category manager. The BTM to DTM assignment follows the same model as the assignment of module Device-DTM to DTM. Vendors are encouraged to define a unique CATID for the protocol between DTM and BTM in order to ensure correct block assignment. The same CATID can be used in different devices if the same BTMs are used.| Presentation objects like ActiveX Conrols do not need to be registered with FDT specific component categories. Actually this sentence seems to be a relict of the FDT 1.2 specification, because the component category for ActiveX and other objects have been removed from the FDT 1.2.1 specification. |
© 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.