Scanned images for crash records may be stored in a centralized location or on a web server and accessed when viewing a crash record in Intersection Magic. Beginning with v6.611, users may use the filter mechanism to specify the a web address or path, filename and even the extension of the image to load. This article describes some ways of using this powerful feature.
When viewing a crash record in the click-on dialog box, (single accident report) there is a button labeled simply “i” for image. Clicking on this button can provide you with a scanned image, web page, or for that matter, any other information related to the current crash record. But first, you have to configure the program to know where to look for your image files.
Select utilities / configuration / default settings / sys settings. Here you have access to a dialog that contains, among other things, a field called App, and a field called File. Both are in the click-on area.
There are three ways to specify the image file to display:
- Launch the file itself, and let Windows figure out the application to launch automatically.
In this case, you will fill in the the “app” field with information to specify the filename to load. The “file” field should simply have (“”) in it.
- Launch the application, and then specify the file to load.
In this case, you will fill in the “app” field with the full path to the program you wish to run. You then fill in the file field with the information that specifies the file.
- Launch a web address that specifies the image file, windows will then launch the default web browser.
In this case, fill in the “app” field with the web address of the image or file you would like to view.
Since both the “app” and the “file” field are parsed as expressions by the program, they must follow the same rules as the filter mechanism in the program. They must evaluate to a string specifying the application, or more often, the file name to be loaded.
Using this method to access the scanned images, means that you should be able to access images in just about any directory, managed by almost any program, using almost any consistant logic.
This routine works very much like selecting Start / Run from the Windows menu and putting in the program and / or file name. If you just put in a file name, that is just like putting a file name in the “app” field. If you put in an application name, followed by a space, followed by some parameters, thats like using the “app” field for the application name, and the “file” field for the parameters.
The “solution” section below gives some examples.
- Simple local case: GIF images stored in DATARECIMAGES directory. Image file names are simply the caseid number with .gif added to the end.
- App: (“datarecimages” + CASE_ID + “”.GIF””)
- Simple network case: GIF images stored in “”n:crash dataimages”” directory. Image file names are simply the caseid number with .gif added to the end.
- App: (“”n:crash dataimages”” + CASE_ID + “”.GIF””)
- Specific application used to access images: A proprietary reader exists which is located in “”r:appsimgreader.exe””. Proprietary IMG images stored in “”n:crash dataimages”” directory. Image file names are simply the caseid number with .img added to the end.
- App: (“”r:appsimgreader.exe””)
File: (“”n:crash dataimages”” + CASE_ID + “”.GIF””)
- Complex network case: TIF images stored in “”\pubworkscrashdataimagesccyy“” directory. Here