In the last exercise, you added a Windows title bar with a custom application title above the Display Manager. In this exercise, you will change the VTS logo that appears on the Display Manager's title bar in order to see the correct use of paths as variable values.
Prior to changing the logo, the image file you wish to use must be saved directly in the Tutorial application's directory. If you do not have a logo with which to practice, copy one from the VTS layer directory's "Bitmaps" directory
(e.g. " C:\VTS\VTS\BitMaps\Icons "). In this example, the "Globe icon.bmp" bitmap has been copied from the "Icons" directory within the VTS layer's "Bitmaps" directory.
1. Stop the Tutorial application.
2. Open the tutorial's "Config.ini" file.
3. Enter "DispMgrBitmap = Globe icon.bmp" as the last line.
4. Save the changes to the "Config.ini" file.
5. Close the "Config.ini" file.
6. Return to the VAM.
7. Select "Tutorial" in the Available Applications list.
8. Click the Run button. The tutorial application runs. The Display Manager should now appear similar to Figure 197.

Figure 197
The examples in this lesson provided only a brief introduction to the many available configuration variables that can be modified in VTS, using the "Config.ini" configuration file, and the other available configuration files.
The VTS Developer's Guide contains information on all configuration files and all their available settings. Please refer to the VTS Developer's Guide for further information.
Skills Achieved in Lesson 18
By completing Lesson 18, you learned the following:
VTS includes a series of configuration files that can be used to adjust the system-wide appearance and behavior of VTS, or can be used to adjust the appearance and behavior of your applications.
You learned that there are specific variables that apply to each of your configuration files, and that these variables must be placed under the correct section heading in order to function properly.
An application-specific Config.ini configuration file is present in the directory of each new standard application you create.
Any modified variables will not become active until the application is restarted.
You now know the basic principles involved in customizing the appearance and behavior of VTS for your application. This lesson provided only a small sample of the vast array of customization options available to you in VTS. Detailed information about the configuration files, their available variables and their use can be found in the VTS Developer's Guide.