----- Unused Variable Checking

08/20/2017 - Update
-------------------
1. Showln output changed to an edit object in the view
2. Command line capability added, 
	parameter 1 = Path and File name
	parameter 2 = 0 or 1 for the output radio buttons.  Default is 0 for output to the edit object
3. The program uses vWin32fh.pkg which has recently been made into a library on vdf-Guidance.com, 
   that is what is now used in this workspace.

04/12/2008 - Update
-------------------
The actual code checking process was removed from the view and turned into a class so 
that it can be included in other applications if desired.  There are four properties 
that can be set in order to call the process

   Property String  psSourceName       // Name of the code file being worked on
   Property String  psOutputFileName   // Output file name for individual use 
   Property String  psOutputPath       // same usage as psOutputFileName
   Property Integer piOutputType       // Output box or output to a file

The variable types searched for can be changed or augmented in one location, gsVarTypes

	
Setup Notes
-------------
Extra local variables are always created in the normal development process, maybe not 
when initially developed but certainly during a rewrite.  By themselves extra variables
they don't really harm anything, but can sometimes be confusing to the developer.

The goal of this program is to either show or output any unused variables to a log file.

A workspace selector isn't provided, operation is thought to be either run the program 
from the Studio or the Hammer tools menu or copy the executable to the programs directory 
of the workspace where you want to check source, or simply use the file dialog to find 
the source you want.  If you do this and select file output, then the log will be written 
to the directory where the source is being checked.

A registry entry will be written that lets the program "remember" the last directory
that was worked in.  

Two outside packages are used, vWin32fh.pkg from vdf-Guidance, and the StringTokenizer
written a long time ago by Torkild Resheim.  The StringTokenizer is provided with this 
application, vWin32fh is not because it's an evolving package and you should obtain the 
library from vdf-Guidance. 

When installing this workspace a new .sws file may need to be created or the workspace converted 
to the DF version being used.  

Delete the vWin32fh library entry and after obtaining the library from vdf-Guidance, add it
to this workspace.

There will be some conditions or variable types that haven't been included or thought of, 
so advise the author if found.  Usually this will show up as a missing method name
or blank variable name.  And usually it's a simple answer -- another trim necessary, or 
a comparison that requires an extra space somewhere.

Bob Worsley
rlworsley@gmail.com