FoxSelect

MENUNEXT=More...

The ^MENUMAX flag indicates that all menus are displayed in a single column, with a More... button at the end of the menu column if needed. When the More... button is selected, the next column of menu items are displayed to the right of the previous col-umn. If the next column of menu entries is too close to the right hand edge of the window, the column is moved toward the left of the window. The MENUNEXT variable contains the text to be displayed on the menu button at the bottom of the menu list.

26. Colors of certain areas of the applications like FoxView or FoxDraw or FoxSelect can change as different programs are executed. The Motif color system, in combination with the Wind/U porting tool causes this.

NOTE

Users should close applications like AIM*, FoxDraw before opening FoxSelect or vice-versa.

27. Whenever time is set back using SMDH, displays containing trend / plot objects need to be re- called to reflect updates.

28. FoxView/FoxDraw/FoxSelect does not support changing time backwards by more than two (>2) years at a time using SMDH.

29. Divide the files into subdirectories, For Example if there are files Config_1 to Config_500 files in /usr/fox/config/Control_Cfg/CIO_STN_Cfg directory, create subdirectories like Config_1_100 and copy all the files from Config_1 to Config_100 into that directory. Follow the same method for all the remaining files, so that the user does not miss any menu items.

30. FoxView supports only 16 trends per display. If we configure more than 16 trends on a display, then up to 16 trends are displayed clearly but for the remaining trends, the trending area appears as blank.

31. When a Pen color is changed in OLTC, sometimes color of the data field does not change accordingly. When this happens, if the cursor is brought on to the data field and right clicked, then the color of the data field is updated to the same changed color in OLTC.

32. (Solaris 10 Operating System Only) FoxView detail display supports only 24 charac-ters in the description field. If we configure more than 18 characcharac-ters in the description field, then up to 18 characters are displayed clearly but for the remaining characters, the description is not shown properly.

5.2 FoxSelect

1. By default, FoxSelect does not Refresh any stations when it is first called in. You must perform a Refresh All, or refresh each station individually. If FoxSelect is started with the ^-REFRESH command line option, FoxSelect refreshes all previously connected stations when it starts up. To start FoxSelect with this option, edit the file

/usr/fox/wp/data/init.user and add the following line:

FS_OPT=-REFRESH

Note, there are no spaces in this line. After editing the init.user file, the workstation must be rebooted.

2. Before connecting to a station in FoxSelect, wait for the Integrated Control Configurator (ICC) to complete a Load ALL or checkpoint, and wait while bus switching is in progress.

3. Whenever a station is refreshed (Options > Refresh) or excluded from refresh (Options > Exclude from Refresh) from the station view, all the active reports clear all their contents. The user has to refresh the report again to list out the compounds or blocks.

4. For Solaris10, FoxSelect does not display last item of the CP list. The last item in the CP list is sometimes not visible. Therefore the user, needs to resize FoxSelect Window to see the entire CP list properly.

5. Solaris (ULTRA 25) AW or WP and Wind/U do not provide support to wheel mouse with any application. Hence, the Wheel mouse functionality on ULTRA 25 (Solaris AW or WP) differs from windows and should be avoided on SOTM.

6. To enable the SSPROMPT functionality, the FS_OPT option must be enabled with the following addition: -ACK. With FS_OPT= -ACK, the pop-up window confirms that you want to turn a compound ON/OFF. (CAR 1008692)

5.3 FoxDraw

1. FoxView reads the user-defined convention file only upon startup. If you add, change, or delete a convention in FoxDraw, the effect of that change does not take place until FoxView is restarted.

2. When a user-defined convention is added, changed, or deleted, remember to copy the updated convention file to all other workstations where displays using conventions are used. User conventions are stored in the following file:

3. The display area is logically a 75.0 (high) by 100.0 (wide) area that occupies the client area of FoxView and FoxDraw. The size of this area is fixed and cannot be changed in FoxView or FoxDraw. However, within FoxDraw, it is possible to drag objects out-side of this area, either partially or entirely. This can occur when using FoxDraw’s zoom out feature, which causes the FoxDraw screen to show an area considerably larger than the 75x100 display area.

A graphic that extends outside the display area causes the workstation to use considerably more memory when the display is called up in FoxView.

An off-screen graphic can be so far off screen that it is not visible in FoxDraw. The only visible indication that a display is defective is that it flashes (because it is being redrawn several times) when called up in FoxView. Also, a defective display eventually causes the workstation to fail.

To determine whether a display has this problem:

Solaris /opt/customer/data/usr_conventions.dat Windows \opt\customer\data\usr_conventions.dat

Within FoxDraw, you can determine whether a display has this problem by choosing Select All from the ^Edit menu and observing where the bounding selection rectangle is drawn.

a. Load the display.

b. Click the ^{Zoom out} button twice.

c. Choose ^{Select All} from the ^Edit menu.

♦ If an off-screen object exists, the bounding selection rectangle extends off screen.

♦ If all objects are within the visible display area, the entire bounding selection rectangle is visible.

To repair a display:

a. Rename the defective display with a name that indicates that it is defective (for example, rename FIC1001.fdf as FIC1001_bad.fdf ).

b. Call up the defective display in FoxDraw.

c. Click the ^{Zoom out} button twice. The area around the display appears.

d. Lasso the 75x100 display area. This selects everything on the visible display.

NOTE

Do not use Select All, which selects everything.

e. Choose Edit/Invert selection.

f. Choose Edit/Delete to delete the items outside the normal drawing area.

g. Save the display as usual.

Examples of defective displays:

One defective display had two lines that extended from -32768 to 32768. Another sample had an entire intact display section copied to a location at 16000. When the off-screen graphics were removed, both displays behaved normally.

FoxDraw can automatically detect and move objects that appear to have invalid coordinates. However, occasionally, valid objects are mis-identified as invalid. The default behavior of FoxDraw is to ignore invalid objects. If you believe that you have a display that might have invalid objects and you would like FoxDraw to check for them, perform the following steps:

a. Using any text editor, create a file called “check_points” in the FoxDraw home directory (/opt/fox/wp/FoxDraw).

b. Open the display in FoxDraw.

If any potentially invalid objects are detected, FoxDraw displays a message box informing you of this. You have the option of ignoring the objects and leaving the dis-play as it is or allowing FoxDraw to move the objects into the valid range. Be sure to save the display if you have FoxDraw move any objects.

4. The ramp operation can only be specified by percentage. You cannot configure a RAMP button to increment by an absolute value. For example, use 50 to ramp a value by 5000 when its range is 10000 to 0.

5. The fdf_to_g and g_to_fdf conversion utilities cannot convert displays containing groups if any group name contains a hyphen ( - ) character or slash ( / ) character.

6. There are a number of reserved words that cannot be used for any of the following:

display file names (including base displays, library objects, and so forth), object names, group names and bitmap names. See the next table for a partial list of reserved words.

7. FoxView and FoxDraw do not support file or directory names containing spaces.

8. The overlapping portion of transparent and opaque objects may be drawn inconsis-tently depending on the orientation and positioning of the objects. Shifting the objects can cause the overlapping portion of the objects to be drawn correctly. The inconsistent rendering of the overlapping portions of the objects has to do with the interference patterns of the fill colors of non-solid objects.

Partial Reserved Word List

9. Copying an object configured with a fill level dynamic and then changing the object

orientation by rotating it causes problems in FoxView with the redrawing of the fill level. To work around this, rotate the object before applying the fill dynamic or deselect the OptimizedUpdate checkbox in the Continuous dynamic configuration dialog box.

10. When converting displays and library objects from .g (ASCII) format to .m1 or .fdf format, make sure to convert the .g file back to its original file type. For example, .g files that were created as displays need to be converted to .fdf format and .g files that were created as library objects need to be converted to .m1 format. Displays and library objects each contain different configuration information, which is generated only when the file is created in FoxDraw.

11. Transparent rectangles configured with a fill level dynamic are not transparent for the non-filled area of the object. If this behavior is not acceptable, use polygons instead of rectangles.

12. If the connection to the FoxAPI or AIM*Server is broken when FoxDraw is running, calling up the browser dialog causes FoxDraw to hang-up until the connection is re-established. The same behavior is seen if the CSA server becomes unavailable.

13. When configuring custom menu entries in FoxDraw, quotes are supported within the command if the quote character (“) is preceded by a backslash (\).

14. Displays and library objects built with the latest version of FoxDraw are generally not backward compatible with previous versions of FoxView and FoxDraw. New features found in the latest FoxDraw is not supported in previous versions of FoxView and FoxDraw. However, if it becomes necessary to move files from FoxDraw V9.0.1 to a previous version of FoxView and FoxDraw, the following steps should be taken:

a. Convert the files to .g (ASCII) format on the latest platform. Use the Display Converter tool in FoxDraw, or use the utility fdf_g for display files and the m1g utility for library objects.

b. If using Windows FoxDraw 9.0.1 or later, the .g file must be converted to be compatible with older versions of FoxView and FoxDraw using the g_back_g util-ity.

\usr\fox\wp\bin\tools\g_back_g <.g files to convert>

c. Bring the .g files to the older workstation, and convert back to their original type using either the Display Converter tool in FoxDraw, or the g_fdf and gm1 utili-ties from a command tool.

15. FoxDraw software must be restarted to affect the mode for case-sensitive tag names.

Stand-alone FoxDraw software restarts automatically. When FoxDraw is restarted, the FoxView button in FoxDraw software is disabled.

16. While configuring a faceplate in FoxDraw software, the compound and block names are not reflected when the faceplate is drawn in FoxDraw software. However, these names are reflected if you save and reopen the display, or select the Configure Object menu for the faceplate.

17. Sometimes, while spacing objects evenly (Layout > Space Evenly) by lassoing objects, it would appear as though FoxDraw software is sorting the objects. In such a scenario, undo the Space Evenly operation. Instead of lassoing and selecting the

objects, shift mouse-click the objects on the screen in the order, and then select Lay-out > Space Evenly to space the objects evenly.

18. When a Display Manager configured display is converted to a FoxView graphic, the

“-c” option does not use the control ranges that were configured in the Display Configurator.

19. When reinstalling stand-alone FoxDraw software on a different drive, set the system variables FOXDRIVE and FOXROOT to the new installation drive. For example, if FoxDraw was installed on the D: drive and then reinstalled on the “C:” drive, the installation procedure does not set the FOXDRIVE and FOXROOT to “C:”. Set these system variables manually using the System applet in the Control Panel.

20. Only msglin command can be configured for close script for base displays.

21. While configuring a faceplate in FoxDraw software, the compound and block names are not reflected when the faceplate is drawn in FoxDraw software. However, these names are reflected if you save and reopen the display, or select the Configure Object menu for the faceplate.

22. Comment objects can not be created with multi-create option.

5.4 DEdit

1. If you have the “Validate Points in Reports” option enabled for a large display with many unavailable or non-existent tag names, it might take several minutes for DEdit to complete checking all of them for the Connection, Complexity, or Exception reports. If you do not need tag names validated for your reports, make sure this option is disabled.

2. DEdit cannot be used to modify linked library objects in displays. This is because the linked library object is a separate file. To modify library objects to be linked into displays, edit those library objects directly with DEdit.

3. When DEdit modifies displays, a number of command tools windows are displayed.

These windows can be ignored.