In order to use the extension, you first need to refer to it. Namely, to register a link to the extension in the compiler's uses directive, while specifying the correct path to the source (or compiled) extension files in the project options. And then create extension objects.

 

Usually, for extended objects, as well as for basic KOL objects, the constructor function NewXXXXX is defined, which returns a pointer to the created object. But sometimes there is no such function, and then the call to the constructor should look like the old Turbo Pascal: new (name_of_object_variable, Create); Here the new function is built in and the Create constructor is provided by all simple Object Pascal objects. Instead of an identifier name_of_object_variable you must provide your own name for the constructed variable.

 

If you have an MCK mirror, if you've installed it, it's even easier to use: just drop the mirror component on the form and configure its options. In this case, from the above list of priorities, there is usually only the indication of the path to the source files in the project property (if these paths are not already known to the compiler).

 

Many components can themselves correctly ensure the presence and correct placement of a reference to the required unit in the uses directive. But sometimes the machine malfunctions, which can lead to misunderstandings. Namely, in the directive uses the reference to the modules of the extension itself and its mirrors fall into the wrong positions when the addition is performed by the Delphi environment itself at the moment of throwing the component onto the form.

In this case, the project refuses to compile, begins to require files that are completely unnecessary for it (the same designintf.pas) or resent the mismatch of the version of the system files. All you need to do is tweak the uses cluster by sending references to VCL units (and mirrors are exactly VCL units) inside protective brackets {$ IFNDEF KOL_MCK}… {$ ENDIF}...