APPLICATIONS MAKER - HELP FOR MISCELLANEOUS TYPES

The  MISCELLANEOUS ITEMS are, as the name implies, items  that  don't
fit any other category.  These items are of six types:  CHECK  INPUT,
BLANK INPUT, CHECK REPORT, BLANK REPORT, DEBUG and COLOR.

CHECK  INPUT ITEMS:  With the CHECK INPUTs the program  will  display
the  input screen for the user.  The page-up, page-down  (etc.)  keys
will  be  active and the user can view the entire  input  screen  via
their use.  No changes can be made to the input screen.  The user may
opt for OK or ABORT.

The CHECK INPUT items take a label as an argument.  If the user  opts
to abort the input, presumably due to a keying error, the application
will do a forward goto to that label.

BLANK  INPUT ITEMS:  With the BLANK INPUTs the input screen  will  be
renewed.   The data entered will be replaced by the squares  you  see
when the application is loaded.

You  may wish to balnk only a certain portion of  your  application's
input screen.  To support this you will be prompted for the beginning
and ending line (vertical) and screen (horizontal), thusly creating a
box within your application in which all items will be renewed.

CHECK REPORT ITEMS:  With the CHECK REPORTs the report screen will be
displayed as with the CHECK INPUT items.  A label on the input screen
is  required as an argument.  The application branches to this  label
if the user aborts the report.

The  CHECK REPORT items also take a label on the report screen.   The
report  is made starting at this label and continues until  the  next
break item on the report screen or the end of the report.

If  the user OKs the report it will be printed from the CHECK  REPORT
screen.   There  is no need to use a DO PRINT item  after  the  CHECK
REPORT item, unless you want two copies of the report.

BLANK REPORT ITEMS:  With the BLANK REPORTs the report screen will be
renewed.   The  data on the report screen will be replaced  with  the
squares you see when the application is loaded.

Like  the BLANK INPUT items you may specify vertical  and  horizontal
limits  within which to blank your report.  Unlike the input  screen,
the  report is of varying width.  Therefore you will need to  specify
the beginning and ending COLUMN (vertical) of the area to blank.

It  should  be noted that each item on the report screen  is  blanked
with SPACES just before it is filled by the program.  If your  report
uses GOTOs to branch around some of it's items you will need to use a
BLANK  REPORT  item  to remove the data they  may  contain  from  the
preceding report, as they may not be executed.

DEBUG ITEMS:  With the DEBUG ITEMS you may interrupt the execution of
your  application as you develop it, and display the content of  your
numeric and string variables.  The debug items will allow you to  see
the numeric OR the string vars.  If you wish to see both at any given
time  use two DEBUG items.  After your application is  completed  and
you have verified it you may remove the DEBUG ITEMS.

This  option  is also available from the edit screen by  pressing  D.
You  may  assign names to your vars.  They will be  saved  with  your
application, and will appear in the DEBUG window thereafter.

COLOR ITEMS:

With the COLOR ITEMS you may create a rectangular area on your  input
screen  that  displays the foreground and background colors  of  your
choice,  provided that you have a machine that can display color  and
that  you  have  not started the program with  the  BW  command  line
argument.

The  COLOR  ITEMS  are unique in that they  are  ignored  during  the
execution  of  your application.  They are executed only  during  the
LOADING  of the application, and can NOT be used to change the  color
of  an area on the screen while running your application.   For  your
convenience   the  COLOR  ITEMS  are  placed  on  the   screen   when
initialized,  and removed from the screen when deleted.   You  should
take care when using these items.

If  you  define  a  small color box, then a  larger  color  box  than
infringes  upon or covers it you will spoil the first box.  You  need
to  define your color areas so that any boxes within boxes are  found
during loading after the larger box.  Failure to do so will result in
a  mess.  As in the execution of the applications, the loading  takes
place from top to bottom, right to left.

You   should  define  your  color  boxes  first,  then   place   your
data/heading items within them.  You CAN do it the other way, but  it
will  be more difficult and take more of your time.  If you  wish  to
add  color areas to an application you may locate your cursor on  the
items  they  contain,  opt to MOVE them then press  return  with  the
cursor  in the same position.  You will then have the opportunity  to
adjust the color of the item without re-initializing it.

