.
                         LISTBOXES
                         =========
.
Listboxes are control objects, owned directly by the form that
 contains them. Just like any other form-control, and the name
 reflects this situation.
.
Until you use (open) a listbox, its hardly any different
than a regular textbox or even a label.
.
Simply clicking on a .listbox will not automatically open it.
 why? maybe the listbox is not prepared with what the programmer
 wants/needs in it.
.
Listboxes, like any other clickable object you create and
 populate the form with, have a USER CODE procedure auto-generated
 for when it gets clicked.
.
If you *want* the listbox to open and let the user pick an item,
 simply say:
     ListPick "formName","listboxName"
in the USER CODE for the listbox. You *could* load the listbox
 and force the user to then pick an item. Then the listpick
 command would be in perhaps some button USER CODE.
.
TECH TIP: you do not have to open the listbox just because it 
 was clicked on. With one command you can if you want to. You can
 open the listbox, forcing the user to pick an item, again with
 the same line of code from anywhere else you desire.
.
example: when you click on a certain BUTTON, the list opens.
. 
  NOTE: once ListPick is called, the user is *forced* to
         choose an item to get the list to close. If you want the
         user to have a "" choice, you have to put it in the list.
.
NOTE: once the list is open, no other click can be acted upon.
.     
NOTE: the '.text' property is what will be displayed when the
      list is closed after choosing an item. If you don't re-set
      the .text property, it won't reflect anything.
.
TECH TIP: listboxes are just appropriately named files. They
          have filenames that reflect their object status.
          The listbox files are in the projects folder.
          You can make your OWN list with NOTEPAD or similar,
          then put the filename in the '.file' property;
          the list will use your custom list.
.
NOTE: if you make your own list file, make sure to place it in
      the appropriate location; IE, in the projects folder.
.
NOTE: the .file property can and should contain the path/ as well
      as the file name.
.
here are the listbox properties:
(x1,y1) and (x2,y2) are FORM coordinate tuples, not absolute

.color;     9 bytes for color; white 255255255 default
.text;      display text, must be set like a label
.x1;        top
.y1;        left
.x2;        bottom
.y2;        right
.border;    if border=1, then the square border is drawn
.data=000;  generic *custom* property anyone can use
.file;      path/filename (under folder 'projects')
.bytes;     # of bytes in list-file; file size
.fieldsize; not implemented yet
.items;     # of items
.index;     last picked item
.autotall;  if autotall=1, then it re-sets y2 for font
.
PROGRAMMING: I know my listbox routine is fairly basic;
             I'm more concerned that it works accurately
             than its the award winning listbox everyone was
             begging for.
.            
PROGRAMMING: if it wasn't for listboxes, you could *almost* use
             'any zany font you felt like'. short single lines
             of text are fine with weird fonts, its the listbox
             that will bomb out if you pick a "system font"
             that isn't true MONO; IE not in the /fonts folder.
.
             so as a TECH TIP, if you avoid listboxes you
             *probably* could get away with using a zany
             font that almost certainly isn't true MONO.
.
PROGRAMMING: .listboxes have an .autotall, great for M-O-N-O
             fonts, which are in the 'fonts/' folder. Hint.
             .listboxes do *not* have an .autowide...
             you have to size a listbox, and that number of
             pixels wide will display a certain number of 
             characters of text.
             this is because listboxes are going to be
             data-driven as a database option;
             .props for this are already going into place.
