T-FLEX Parametric CAD. Fundamentals. 2D Design

Macros
References are required for accessing properties, methods and events of a particular object and for using this
object while programming a macro. For example, to use T-FLEX CAD commands in a Project, you would
need to reference TFlexAPI.dll. At the time of creating a new project, main references are already added to it
for using Microsoft Windows and T-FLEX CAD objects.
The «Projects» window, just like the «Macros» window, displays all
currently opened Projects from T-FLEX CAD files, as well as Projects
from the files located in the special folder «/Program/Macros». These two
windows are synchronized. Closing a Project (document) file in T-FLEX
CAD also makes it close in the «Projects» window of the macro editor.
Similarly, a macro that has been created and made executable in the
Macro editor consequently appears in the «Macros» window of T-FLEX
CAD.
Project elements are displayed in this window as a hierarchical structure.
Displaying project elements as a tree simplifies viewing and selecting
them. The project contains folders with modules, forms and references.
There are two alternatives to add a new element to a project:
• Right clicking the desired folder (for example, «Modules») lets
•
you access the option «Add» in the context menu. After selecting
this option, the respective element will be added. When adding a
reference, an input box appears for the user to type in the reference.
Alternatively, a new module (form, reference) can be created by
selecting an appropriate option on the «Project» toolbar.
As it was mentioned earlier, each Project can contain an unlimited number of macros (procedures). To tackle
the issue of repeating macro names, T-FLEX CAD uses namespaces. A namespace is an area of a program
within which a macro (procedure) name must be unique. Use of namespaces helps working with a large
number of macros. Namespaces are used as a convenient way of structuring a large number of macros. By
using a namespace, one can create two macros with the same names within a common project. In this way,
the macros will belong to different namespaces. This approach implies uniqueness of names of namespaces
themselves. The names of namespaces should preferably reflect on their purpose as well.
743