After the SRP Application Launcher has been installed there will be several files (in addition to this read me document) added to your OpenInsight folder:

  • SRPApplicationLauncher.exe
  • SRPApplicationLauncher.INI
  • SRPApplicationLauncher.png
  • SRPControls.ocx

Each of these files is documented below.

SRPApplicationLauncher.exe

This is the actual program that launches OINSIGHT.exe for you. You can rename it to anything you want (e.g. MyApp.exe). The icon can only be changed using a resource editing tool such as Resource Hacker or Icon Changer. Alternatively, if you send us an icon, SRP will do this for you at no charge.

SRPApplicationLauncher.ini

Configuration information for the launcher is stored here. This file must be in the same directory as SRPApplicationLauncher.exe. You may rename this file as long as it matches the name of the launcher (e.g. MyApp.exe and MyApp.ini). If you open this file up in a text editor most of the information should be self-explanatory. For detailed information, see the references that follow:

SRPApplicationLauncher.PNG

This is the default splash screen shamelessly advertising SRP Computer Solutions, Inc. You can use any image you want for a splash screen, but feel free to share this with your friends.

SRPControls.ocx

This is where the SRP Launcher Control is maintained. We include it with the SRP Application Launcher because it is used to provide the enforcement of single-instance execution of an application. You will need to put this on your main application form and use the ProgID of SRP.Launcher.1. Set the OLE control to be invisible using the control properties dialog. The SRP Launcher executable communicates directly with this OLE control to establish whether or not another instance is already running. If it is, then the launcher aborts the attempt to run OINSIGHT.exe again and brings the main application to focus.

Additionally, an OLE event, OnLaunchAttempt, will fire. The syntax is:

OnLaunchAttempt(CommandLineParams)

It is optional if you want to intercept this event. One use of this event is to capture regular or custom command line parameters. This will allow the application to determine if they are important and if there is a need to respond. The command line parameters are passed in the CommandLineParams parameter of the event. For example, you could check for a request to run a backup:

Convert @LOWER.CASE to @UPPER.CASE in CommandLineParams
Locate "/B" in CommandLineParams using " " setting Pos then
Call Run_Backup_Process()
end

Because this is an OLE control, it will have to be registered. From a command line, type the following:

regsvr32 <path>\SRPControls.ocx

OCX files can be located anywhere. However, it is recommended that you either leave it in your root OpenInsight folder or move it to your System32 folder.

  • No labels