|
DigiPara Liftdesigner LDX API
|
Documents are handled via the main ILDXApplication5 object. How you get to that object depends on your situation.
classDiagram
class ILDXDocument5
class ILDXDocuments
class ILDXApplication5
class IModel
class IView
class LDOOP.ILDOOPServer
class LDOOP_UI.ILDOOP_UIApplication
ILDXDocuments ..> ILDXDocument5 : .Item(), enumeration
ILDXApplication5 ..> ILDXDocument5 : .ActiveDocument
ILDXApplication5 ..> ILDXDocuments : .Documents
IView ..> IModel : .Model
IModel ..> ILDXApplication5 : .LDXApp
LDOOP.ILDOOPServer ..> ILDXApplication5 : .Application5
LDOOP_UI.ILDOOP_UIApplication ..> ILDXApplication5 : .Application5
From the ILDXApplication5, you can access the collection of all documents, ILDXDocuments, via .Documents. From there, you can access the open documents via standard foreach enumeration (See Close .ld3 file and Check LDXDocument is opened in DigiPara Liftdesigner).
From the ILDXApplication5 itself, you
You close documents with .Close (See Close .ld3 file).
For every COM interface, we define a default implementation via a coclass. The interface name will start with I and typically end in 5, as these interfaces were first defined in this form in Liftdesigner version 5. The coclass has this prefix and suffix stripped. Example: The coclass for ILDXComp5 is LDXComp. This documentation uses the interface names as much as possible. The .NET wrappers, however, map everything to the coclasses; therefore, the VB.NET samples use the coclass names.
Next: Data Tree