Full-View - Windows for Pick

1. You should perform a FILE-SAVE prior to loading FULL-VIEW. This FILE-SAVE is not likely to be used, but in case something goes astray, having a copy of your data is good insurance.

   
   

2. You should log users off of your system and allow it to write all frames to disk.
   

1. Loading the FULL-VIEW account which contains all of the programs, data files, and drivers necessary for FULL-VIEW to operate.

   
   

2. Booting the system to load the FULL-VIEW ABS and MONITOR code.

   
   

3. Specifying the terminal configuration for each terminal on the system.

   
   

4. Setting up the user accounts which need to utilize FULL-VIEW.

   
   

5. Starting windowing for each port or application that is to use FULL-VIEW.
   

Specific information about loading FULL-VIEW is included in on-line documentation included with FULL-VIEW. In that this information can change quite frequently and is nearly always different for each type of system on which FULL-VIEW is loaded, it will not be discussed in detail here.

    SET-FLOPPY (HA
    T-REW
    T-LOAD MD (O
    INSTALL

When the INSTALL proc executes, it will restore an account names FULL-VIEW, copy a number of items into the system ERRMSG file, and add a command to the SYSTEM-COLDSTART routine that actually loads the run-time FULL-VIEW ABS and MONITOR code. You then need to shutdown and reboot your system to actually execute the FULL-VIEW startup proceedure.

FULL-VIEW terminal drivers have descriptive names. These drivers are actually definition items held in a data file. To list the available drivers, choose the selection on the FULL-VIEW account menu that runs an ACCESS listing of the terminal drivers. Hopefully, you will see an appropriate driver for the terminal that you are using. Some common drivers are:

• PICK.MONO A monochrome (not composite) PC port 0 monitor
  
• PICK.COLOR A color (or composite) PC port 0 monitor
  
• FUJ.COLOR A color Fujitsu port 0 monitor
  
• WY60 A Wyse 60 in native emulation mode
  
• WY50 A Wyse 50 in native emulation mode
  
• WY50-VP A Wyse 50 in viewpoint emulation mode with enhanced on
  

Carefully read the section in this manual on terminal driver definitions, then refer to your terminal manual to determine what control sequences drive your terminal for nearly every conceivable function. Manually enter a new terminal table using the DEFINE FULL-VIEW TERMINAL selection on the FULL-VIEW account menu.

If you hit something that stumps you, contact Modular Software Corporation for technical support. Actually, defining a terminal is not that difficult once you are familiar with the process.

When you first enter the demo, you will be presented with a FULL-VIEW window oriented menu. Operating the menus is quite easy. Simply press a key to execute a desired menu selection, or, use the cursor keys or space bar to highlight the desired selection and press the [RETURN] to execute the selection.

The demo menu has selections that demonstrate windowing functions, data-entry functions, SMART-TREE lookup and DEFINE-KEY functions, as well as other topics of interest to users and software developers.

Next, you will probably want to add some commands to the logon PROC in your account. Specifically, you will want to add:

    FV-INITPORT
    P
    HSET-HOT-KEY D ;
    H 140 = RUN FV.BP TCL-SHELL ;
    H 250 = RUN FV.BP PRINT-SCR
    P

After you have executed this new logon PROC, you should notice that you are operating with a TERMTYPE of "mm-mon". This TERMTYPE letter is matches the "virtual terminal" of FULL-VIEW, regardless of what actual terminal type you are using.

You will now need to create some data files if you are going to use some of the FULL-VIEW utility functions. These data files are SCR.SOURCE and SCR.OBJ if you are going to use the data entry screens, MENU.SOURCE and MENU.OBJ if you are going to use the menu processor, and HELP.SOURCE and HELP.OBJ if you are going to use the help window painter and subroutines. Actually, you may not want to create these files in your development account but actually in another account that is used to hold program-type files. Then set up Q-pointers to these files from many different accounts.

You are now ready to start working with FULL-VIEW.

1. If your screen doesn't look right in the demo account, you probably have an improper terminal driver setup. Check the driver and also check to be sure that your terminal is in the proper emulation mode.

   
   

2. If your screen still doesn't look right, check to be sure that windowing is turned on and that the TERMTYPE is set to "mm-mon". Type TERM at TCL to check this. If it is not, a FV-INITPORT command at TCL should activate windowing.

   
   

3. If function keys or cursor keys on your keyboard do not work correctly, this means that the characters they are sending do not match the characters in the terminal driver table. The driver tables are usually designed for the factory default function key definitions. Programming other strings into terminal function keys will prevent them from operating with FULL-VIEW. Try programming the shifted function keys for your application response strings and leaving the un-shifted function keys in default mode.
   

Next, try starting a window on the screen with a command like:

    START-WINDOW 5,75,2,22

    START-WINDOW

This should get you started. For additional information and examples, refer to the FULL-VIEW Demo examples and the on-line help included with FULL-VIEW.