========================================================================
    WIN32 APPLICATION : poly-view Project Overview
========================================================================

AppWizard created this poly-view application.  

This file contains a summary of what you will find in each of the files that
make up the poly-view application.


poly-view.vcproj
    This is the main project file for VC++ projects generated using an Application Wizard. 
    It contains information about the version of Visual C++ that generated the file, and 
    information about the platforms, configurations, and project features selected with the
    Application Wizard.

poly-view.cpp
    This is the main application source file.

/////////////////////////////////////////////////////////////////////////////
AppWizard has created the following resources:

poly-view.rc
    This is a listing of all of the Microsoft Windows resources that the
    program uses.  It includes the icons, bitmaps, and cursors that are stored
    in the RES subdirectory.  This file can be directly edited in Microsoft
    Visual C++.

Resource.h
    This is the standard header file, which defines new resource IDs.
    Microsoft Visual C++ reads and updates this file.

poly-view.ico
    This is an icon file, which is used as the application's icon (32x32).
    This icon is included by the main resource file poly-view.rc.

small.ico
    This is an icon file, which contains a smaller version (16x16)
    of the application's icon. This icon is included by the main resource
    file poly-view.rc.

/////////////////////////////////////////////////////////////////////////////
Other notes:

poly-view.cpp	- main application - window pump, etc.
load-poly.cxx	- class to load poly files
parseargs.cpp	- parse command argument
poly-load.cxx	- load poly functions
poly-paint.cxx  - paint the loaded polys
poly-utils.cxx	- utility functions
sprtf.cpp       - diagnostic output to a file temppolyv.txt

/////////////////////////////////////////////////////////////////////////////
Command Line:

Usage: <limit> <work-folders>

e.g.
--chunk=e150s40 --work-dir=test\work\LandMass --work-dir=gshhs\lm_gshhs

Or: <work-file>

e.g.
--work-file=gshhs\lm_gshhs\e150s40\e150s31\5410496.2204

Or: <work-dir>

gshhs\lm_gshhs\e150s40\e150s35

Many other options, like the new

--fg-scenery=<path> will load existing scenery for
the 'buckets' involved... and will load off a network... like -

File: /\Dell02/scenery-1.0.1/Terrain/e150s40/e151s34/5426697.stg
File: /\Dell02/scenery-1.0.1/Terrain/e150s40/e151s34/5426697.btg.gz

--nudge=0.008 --work-file=test\work\LandMass\e150s40\e151s34\5426697.49 --nudge=0.0 --work-file=gshhs\lm_gshhs\e150s40\e151s34\5426697.2181 --fg-scenery=\\Dell02\scenery-1.0.1
--nudge=0.008 --work-file=test\work\LandMass\e150s40\e151s34\5426697.49 --nudge=0.0 --work-file=gshhs\lm_gshhs\e150s40\e151s34\5426697.2181 --fg-scenery=C:\FG\Scenery-1.0.1

/////////////////////////////////////////////////////////////////////////////
Program Notes:

Getting coordinate system, and translation to screen pixels
From: load-scene.cxx
From:      clat) -0.590139,      clon) 2.641992, got xyz -4656423.000000,2541401.000000,-3529151.500000 from xyz_lat(-33.8125,151.3750)
From: Map (of Atlas)
From: theta(lat) -0.591255, alpha(lon) 2.640674, got xyz -4649607.500000,2545639.000000,-3535038.000000 from xyz_lat(-33.8764,151.2995)
So these are the SAME...
