This file covers the following items:

=================================================================
>   TRIAL VERSION LIMITATIONS

>   INSTALLATION

>   NEW PROPERTY AND ENHANCEMENTS

>   GTSIZER FILES

>   KNOWN PROBLEMS

>   ORDERING
=================================================================

*****************************************************************
TRIAL VERSION LIMITATIONS
*****************************************************************
The GTSizer trial version will run only when Delphi is running
AND at least one form containing the GTSizer trial version is open 
in the Delphi Editor.

To evaluate the trial GTSizer's performance at different 
resolutions, first compile your application at one resolution.  
Minimize Delphi. Then run your application's EXE at various 
resolutions.  If you must restart your computer to change 
resolutions, be sure to launch Delphi before running your 
application's EXE.  (You can minimize Delphi.)

DO NOT SELECT RUN FROM WITHIN DELPHI'S IDE AFTER YOU HAVE 
INITIALLY COMPILED YOUR APPLICATION.  Selecting RUN will 
recompile the application at the new resolution and will not 
allow you to properly evaluate the GTSizer's usefulness. 

*****************************************************************
INSTALLATION
*****************************************************************

Installing the GTSizer is a three step process:

1) Launch the GTSizer setup application (GTSETUP.EXE).  This will
copy your GTSizer files to the appropriate directories and 
integrate the GTSizer's help system with Delphi's help system.  
Note that the default path is 
	C:\Program Files\Borland\Delphi 3\GTSizer

2) Include the GTSizer in Delphi's library path.  You can include
the path to the GTSizer files through the Tools | Environment 
Options--Library page.  You can also add the GTSizer path to your 
system Path environment.  Otherwise you may receive a compile 
error "...cannot find GTSIZE32.DCU"

3) The GTSizer must then be installed to Delphi's component 
palette.  

*INSTALLING GTSIZER TO THE COMPONENT PALETTE*

You may either (1) install GTSizer package using the GTSIZER.DPL 
file OR (2) install GTSizer DCU files into the existing User 
Package (dclusr30.dpk).  DO NOT DO BOTH!

(1) To install the GTSizer package:

>  Launch Delphi 3.  From its main menu, choose 

	Component | Install Packages

   The Packages page of the Project Options dialog box will 
   appear.  

>  Click the Add button.  The Add Design Package dialog box will 
   appear.  Select the GTSizer directory and highlight the file 
   GTSIZER.DPL so that it appears in the File Name edit box.     
   Then click OPEN.

The Packages page will reappear and GTSize32 v 2.1 (Trial) will
appear at the bottom of the Design Packages box.  Click OK to 
close the dialog box.

**OR**

(2) To install the GTSizer into the Package dclusr30.dpk:

>  Launch Delphi 3.  From its main menu, choose
	
	Component | Install Component

The Install component dialog box will appear.  

>  In Unit File Name, click BROWSE, select the path for the 
   GTSizer, and highlight the file GT32Reg.pas.  Click OPEN.

The install components dialog box will appear.

>  Click OK

You will receive a message "Package dclusr30.dpk will be built 
then installed.  Continue?"  

>  Click YES

A change dclusr30.dpk confirmation box may appear with the 
message "The following changes are necessary to make this 
package compatible with other installed packages"  

>  Click OK

You will then receive an Information message 
"Package: {Path}\dclusr30.dpl has been installed.  The following 
new components have been registered. GTDBForm, GTForm."  

>  Click OK

>  Close the Package form by clicking the X on the top right corner.

A Confirm dialog box will appear with the message "Save changes 
to dclusr30.dpk?

>  Click YES

Regardless of which package you use, the GTSizer controls will 
appear on the Component Palette as follows:

	GTSizer (hint name GTForm) on the Additional Page
	GTDBSizr (hint name GTDBForm) on the Data Controls Page
 
GTForm and GTDBForm are the ClassNames for the components 
marketed under the name GTSizer.  The GTSizer (GTForm) has a blue 
background and the GTDBSizr (GTDBForm) has a white background.

If you wish to customize the component placement on the component 
palette, use the GT32Reg.PAS file to do so.  Simply replace the 
name in the Find RegisterComponent statement to the desired 
palette page name. (See the notes in the GT32Reg.PAS file)  


*****************************************************************
NEW PROPERTY AND ENHANCEMENTS
*****************************************************************

*NEW PROPERTY:  IGNOREFONT*
The IgnoreFont property allows you to determine which number you
wish the GTSizer to look for in the control's Tag property.  As a
designer you may not want GTSizer to resize the font for all 
controls.  Previously, you would use a value of 1 in the tag 
property to indicate which control's font not to resize.
However, some developers were already using the number 1 in the 
Tag property and had to alter their code and change it to another 
number.

In this version, the Tag property can be any number you choose.  
Just set the GTSizer's IgnoreFont property to the number you will 
use in the control's Tag property.  The GTSizer will not resize 
the font of any controls where the tag property contains the same 
value as the IgnoreFont property value.

*ENHANCEMENT:  SCREEN REFRESH*
This GTSizer release refreshes the screen much faster than 
previous releases.

*ENHANCEMENT:  FOCUS*
Previously, some users who set focus to controls received the 
message "Cannot focus a disabled or invisible control".  If you 
have this problem or wish to avoid it entirely, use the following 
code to set focus of any control at run time:

	GTForm1.Focus(NameOfControl);

For example, if you were setting focus to a control named Edit1 
you would use:

	GTForm1.Focus(Edit1);

instead of

	Edit1.SetFocus;

If you are setting a control's focus on a tabbed notebook or page 
control, be sure that the page containing that control
is visible and is also the current page.

*ENHANCEMENT:  CONTAINERS*
Container objects such as scroll boxes will resize normally, even 
when they contain controls which are considered outside the 
bounds of the form.  

*********************************************************************

GTSIZER FILES

*********************************************************************

After running the installation program, you should have the following 
files:

GT32reg.pas
GTDBForm.dpr
GTDBSizr.pas
GTReadme.txt
GTSize32.dcr
GTSize32.dcu
GTSizer.cnt
GTSizer.dpl
GTSizer.hlp
License.txt
PReg32.dpr

Sample applications are included in the GT32DEMO directory.  These 
applications were created at 800x600 small fonts.  It is best to
compile these sample applications at 800x600 small fonts, because
compiling at any other resolution may require some adjustments.  
You can then test the EXE files for the samples at various
resolutions.  The sample files have three subdirectories (GTMDIDEM, 
GTRTMDEM, and GTSDIDEM) and their associated files:

*GTMDIDEM*  
(Example of using the GTSizer in an MDI application)

GTMDIApp.dpr
Main.dfm
Main.pas
Maindemo.dfm
Maindemo.pas
Ordrinfo.dfm
Ordinfo.pas
Rescover.dfm
Rescover.pas

*GTRTMDEM*

(Example of using the GTSizer with controls added or deleted at run 
time)

GTrtmapp.dpr
RTMCtrls.dfm
RTMCtrls.pas

*GTSDIDEM*
(Example of using the GTSizer in an SDI application)

GTFlash.dfm
GTFlash.pas
GTSDIApp.dpr
SDILabel.dfm
SDILabel.pas
SDIMain.dfm
SDIMain.pas
SDIRescv.dfm
SDIRescv.pas

*****************************************************************

KNOWN PROBLEMS

*****************************************************************

*MDI Forms*
Due to changes Borland has made to MDI forms in Delphi 3, the 
GTSizer is not currently able to support the Main Form (form 
style MDIForm).  However, it does support MDI child forms (form 
style MDIChild).  

*Duplicate GTSizer Recognition*
Only one GTSizer is needed per form.  It is best to add the 
GTSizer by selecting it from the component palette and clicking 
anywhere on your form.  Because the GTSizer is a component that 
requires only one per form, it attempts to delete any previous 
GTSizer found on your form.

When the GTSizer icon is double-clicked from the component 
palette, the form may not be fully focused when the code is run. 
So, it may remove the previous GTSizer from your form but the 
declaration may still be present in the unit file and you will 
receive an error message.  If this occurs, delete the declaration 
before dropping the GTSizer again on your form.  

===================================================================
ORDERING
===================================================================

GTSizer is US$99.95 for a single developer license.  There are no 
runtime licenses or royalty fees.

Order from 

GenoTechs, Inc.
2741 West Southern Avenue #10
Tempe, Arizona 85282 USA

Tel:  602-438-8647
Fax:  602-438-8654
e-mail:  genotex@genotechs.com
http://www.genotechs.com

We accept checks payable in US dollars and drawn on a US bank, 
credit cards (Visa, Mastercard, American Express, Diners Club, 
and JCB), and bank wire transfers (e-mail for bank routing
number).















