Blueworx Voice Response windows become active without being selected

If you start Blueworx Voice Response and the windows display correctly but become active without being explicitly selected, the window manager may be using the wrong keyboard focus policy.

The window manager focus policy is set in a file called .Xdefaults. The master .Xdefaults file is included in the AIXwindows software. However, anyone who uses the system can copy the .Xdefaults file into their own directory and edit it to suit their preference.

If you are using AIX windows

Use this procedure to change the keyboard focus policy.

Start

Log on as dtuser, or if you are already logged on as root, reset the environment (see Setting the Blueworx Voice Response environment).
To make sure you are in the home directory, type the following command and press Enter:
```
cd $HOME
```
To display the contents of the directory, type the following command and press Enter:
```
ls -a
```
Look for a file named .Xdefaults. If the file is not there, use the AIX documentation to find out where else to look.
Edit the .Xdefaults file.
Find the lines that specify the keyboard focus policy. Make sure they read as follows:
```
Mwm*focusAutoRaise:true
```
```
Mwm*keyboardFocusPolicy:explicit
```
Save your changes.
Type the following command and press Enter:
```
xrdb $HOME/.Xdefaults
```

The keyboard focus policy is now correct.

If you are using the common desktop environment

Use this procedure if you are using the common desktop environment (CDE).

Start

Log on as dtuser and start the common desktop environment.
Click the Style Manager icon.
In the Style Manager, click the window icon.
In the Style Manager Window, click Click in Window to Make Active and Raise Window When Made Active.
Click OK.
Restart the common desktop environment.

The keyboard focus policy is now correct.