| Class TInstallBDE (unit Instbde) |
Exceptions
| Constructors |
constructor Create(AOwner: TComponent);| Functions |
procedure AfterInstall;
procedure ConfigureIdapi;
destructor Destroy;
procedure DoIDAPILangDrv;
procedure ExpandPaths;
procedure Install;
function IsIdapiRunning: Boolean;
procedure Loaded;
procedure Refresh;
procedure DoExternalComponentCall(Install: TInstall;ComponentCall: String;PO: TObject);
procedure SetAddTheFiles(Value: Boolean);| Properties |
property AddTheFiles : Boolean| Events |
event OnFixFailed : TNotifyEvent
event OnMergeFailed : TNotifyEvent| Variables |
PreviousExternalComponentCall : TExternalComponentCall;
DestDLL : String;
DestinationConfigName : String;
DestinationConfigPath : String;
DestLD : String;
ExistingCfg : String;
FAddTheFiles : Boolean;
FFixFailed : TNotifyEvent;
FMergeFailed : TNotifyEvent;
GoodToGo : Boolean;
InstalledCfgFile : String;| Constructors |
constructor Create(AOwner: TComponent);TInstallBDE
| Functions |
procedure AfterInstall;
procedure ConfigureIdapi;
destructor Destroy;
procedure DoIDAPILangDrv;
procedure ExpandPaths;
procedure Install;
function IsIdapiRunning: Boolean;
procedure Loaded;In case we somehow get "freed", we do not want to create a gap in the "back-chaining", so we will relinquish control of the event handler to the component that took it before us... A fair shake if I may say so myself.
procedure Refresh;This is where we deciede whether or not we want to intercept this event.
procedure DoExternalComponentCall(Install: TInstall;ComponentCall: String;PO: TObject);Well, we want to be able to intercept "external component calls" made by the TInstall componet (or for that matter, any component that is installing itself). To do this we assign an event handler to the ExternalComponentCall event of the TInstall component. However, there will probably be components before us that also want to handle the event. So what we do here is remember who was before us so that when it is our turn to handle the event, we will be "unselfish" and let the person before us call handle the event and after he/she/it is done, we will call our event handler. In essence, we have a "back-chaining" of this event call.
procedure SetAddTheFiles(Value: Boolean);| Properties |
property AddTheFiles : Boolean| Events |
event OnFixFailed : TNotifyEvent
event OnMergeFailed : TNotifyEvent| Variables |
PreviousExternalComponentCall : TExternalComponentCall;
DestDLL : String;Language driver directory.
DestinationConfigName : String;Path of the default destination directory for the idapi configuration file.
DestinationConfigPath : String;Path and name of the IDAPI.CFG file that is on the user's computer.
DestLD : String;Where the IDAPI.CFG, that is in the installation got installed.
ExistingCfg : String;
FAddTheFiles : Boolean;
FFixFailed : TNotifyEvent;DLL directory.
FMergeFailed : TNotifyEvent;
GoodToGo : Boolean;
InstalledCfgFile : String;file name of the idapi configuration file.