VBVConfig is a configuration tool that makes it easier for you to configure a VBVoice development environment or application. With VBVConfig, you do not need to edit .INI files directly. You can search for a key by its name, value, description, or type. You can view all keys or keys of just one section. You can manage multiple .INI files within VBVConfig.
VBVConfig also offers a Version Info Utility that searches for files specified in .VVC files and then displays the version information of these files in a table. This tool is useful for troubleshooting file version problems.
There are three ways to find a key in VBVConfig:
Browsing for a Key |
The left pane of VBVConfig lists INI files that are defined in the .VIC files located in the VBVConfig directory. By double clicking on these files, you can navigate to the INI files. This is a good way to search for a key if you know its name. The items that appear below an INI file when the tree is expanded are called sections. Each section contains at least one key. Click on a section and its keys are displayed in the right pane. |
Searching for a Key |
Select the Find command from the Edit menu. Use this command to search for keys by specifying a string of text to search for within selectable properties of the keys. This is a good way to search for a key if you do not know its location. If you hit Enter and the returned key is incorrect, resume your search by hitting F3. The next key found matching your specified criteria is displayed. |
Viewing all Keys |
In the left pane of VBVConfig, the highest tree item is the (All-Keys) item. By clicking on this item, the program scans through all the keys defined in the .VIC files and presents them in a large list that you can sort by name, section, value, or file. This search method helps you find a group of keys with similar values and it helps you get a better sense of what you can configure in VBVoice |
After finding the key you want to modify, double-click on it to view the corresponding edit-value dialog box.
VBVConfig can now manage multiple .INI files of the same type. Specify the .INIs that you want VBVConfig to manage under File Locations in the Tools menu.
The default files that VBVConfig manages are:
|
|
|
|
Each of these files is located in the Windows directory and has a type equal to its filename without the .INI extension. You can change the location of these files or add another file to the list.
You can also choose to manage only those files that exist. Enable this option under Show Only Existing in the Tools menu. If disabled, all settings shown in an .INI file are the defaults. Any change to a key results in the creation of the .INI file.
After you have changed a key value, hit OK or Apply. You can choose to save your changes to the INI files on disk so that VBVoice can use your configuration settings.
Click on the File menu to view the options for saving your changes:
Save just the selected key
Save all changes to the keys in the current section
Save all changes to the keys in the current INI file
Save all changes to all keys in all sections of all files
VBVConfig provides a tool that you can use to examine the file versions of all the VBV Binaries. Click on Version Info in the Tools menu to open up the Version Info Utility.
When you open the tool, it scans the standard directories for binaries information. The standard directories are $Windows$, $windows$\System, $windows$\system32, one directory level above VBVConfig, and all of VBVConfig subdirectories. If you need a more thorough search of your hard disks for binaries, use the Scan All Menu function to search all the hard disks for VBV binaries and their version information.
To send Pronexus technical support your file version information, export the table contents in the Version Info window by selecting Export List to TSV File under the Filemenu.
You can edit the list of files that you want VBVConfig to manage in a configuration window. Select File Locations from the Tools menu to open this window. Clicking the white on blue cross adds a new file to the list, whereas clicking the white on red X removes the currently selected item from the list.
When adding a file, you can specify any location accessible by Windows Explorer, but note that network paths and paths on removable media can significantly slow VBVConfig when the files do not exist. Added files may have any name, but their type must be one of: vbvoice, annc32, vbvrtm or wapsvr. VBVConfig uses these types to identify the files that may accept key definitions from the .VIC files present in VBVConfig's startup directory.
VBVConfig creates the key hierarchy by reading definitions from the .VIC files present in its startup directory. You can edit these .VIC files manually to change the keys that VBVConfig manages.
The .VIC file format is detailed below:
<Section_Name>~<Key_Name>~<Key_Type>~<Possible_Values>~<Default_Value>~<Ini_Name>~<Description>
Where:
<Ini_Name> |
Type of INI file (must be one of vbvoice, annc32, vbvrtm or wapsvr) |
<Section_Name> |
Section name in which the key resides (without the [ or ]) |
<Key_Name> |
Key name (that is, the text before = in the .INI file) |
<Description> |
Text string explaining the function of this key |
<Key_Type> |
Can be one of: |
|
1. number: This key should take an integer value <Possible_Values> Specifies the range in the format: <minimum>^<maximum> (i.e. 0^100) |
|
2. flag: This key should take a 0/1 value <Possible_Values> Serves no purpose |
|
3. text: This key should take a string of text <Possible_Values> Serves no purpose |
|
4. path: This key should take a full directory path. <Possible_Values> serves no purpose |
|
5. file: This key should take a full file path <Possible_Values> Serves no purpose |
|
6. list: This key should take a string of text from a list of possible values <Possible_Values> Specifies the list of possible strings in the following format: <op1>^<op2>^...^<opN> (i.e. Option 1^Option 2^Option 3) |
|
7. list2: This key should take a string of text equivalent to an option displayed to the user <Possible_Values> Specifies the list of possible values and their displayed strings in the following format: <op1>=<disp1>^<op2>=<disp2>^...^<opN>=<dispN> (i.e. Option 1=First Option^Option 2=Last Option) |
|
8. digit: This key should take a character equivalent to the digits available on a touch-tone phone <Possible_Values> Serves no purpose |
|
9. cstts: This key should take a string specifying the location of a TTS server <Possible_Values> Is not documented |
If you do not want to modify the large Config.vic file, there is another method for removing keys from VBVConfig's view, using a file named Exclude.uic, which must reside in VBVConfig's startup directory.
The format of this file is identical to the .VIC files, except that VBVConfig ignores all the fields except <Ini_Name> , <Section_Name>, and <Key_Name>. When VBVConfig encounters a key specified in this file that exists in one of its managed files, it removes the key from view. So, you can disable a key from being managed by copying a line from Config.vic into Exclude.uic.