Tab Pro Version 2.0  
README  
FarPoint Technologies, Inc.  
------------------------------------------------------------------  
  
The following topics are available:  
	Release Notes
	Installing Tab Pro Version 2.0  
	Installed Files	  
	Upgrading Existing Tab Pro Version 1.1 Projects  
	Upgrading Existing Tab/VBX Version 1.1 Projects  
	Additional Information for C and C++ Users
	Corrections to the User's Guide  
	Corrections to the Reference Guide  
	Contacting FarPoint Technologies  
  
  
*** Release Notes ***

- If you plan to redistribute Tab Pro controls, please refer to the 
  REDIST.TXT file for a list of files you must distribute with your 
  application. The REDIST.TXT file is installed in your \TABPRO20 
  directory.

- To place child controls on your Imprint or Tab OCX controls at 
  design time, your container must support ISimpleFrameSite. If your 
  container does not support ISimpleFrameSite, you must add child controls
  at run time.

- Caution: If you are applying an AutoStyle to your Tab control, to avoid
  losing property settings, apply the AutoStyle immediately after you 
  create the Tab control and before you set other properties. If you have 
  already changed characteristics of your Tab control, be aware that 
  applying an AutoStyle may change those characteristics. Also, note that 
  applying an AutoStyle to a Tab control that contains child controls may
  create unexpected results.

- At design time in the Properties window or in the property pages, the 
  AutoStyle property always has the value of 0 - Reset, even if you just 
  applied an AutoStyle to the Tab control. This is because the AutoStyle 
  property represents a one-time action applied to the Tab control.

- You cannot double-click a control in the toolbox to make it a child of 
  an Imprint or Tab control. You must select the control, and then draw 
  it in the Imprint or Tab control. If you double-click a control in the 
  toolbox, it becomes a child of the the form; it does not become a child 
  of the control with the focus.


*** Installing Tab Pro Version 2.0 ***  
  
Use the installation program, SETUP.EXE, on the distribution disks to  
install Tab Pro. You cannot copy the contents of the distribution disks 
to your hard disk because the information is compressed on the disks.  
Program files must be decompressed and installed in the appropriate  
directories to run properly.  
  
To install Tab Pro from the MS-DOS prompt  
  
1. Place the Tab Pro Disk 1 in the drive and type   
      WIN A:\SETUP  
   assuming that the drive is A.  
  
2. Follow the instructions on the screen.   
  
To install Tab Pro from Windows 3.1 or Windows NT  
  
1. Place the Tab Pro Disk 1 in the drive.  
  
2. In Program Manager, choose Run from the File menu and type   
      A:\SETUP   
   assuming that the drive is A.  
  
3. Follow the instructions on the screen.   
  
To install Tab Pro from Windows 95  
  
1. Place the Tab Pro Disk 1 in the drive.  
  
2. Choose the Start button, choose Run, and type   
      A:\SETUP   
   assuming that the drive is A.   
  
3. Follow the instructions on the screen.  
  
If you receive an error message while running the installation program,  
restart Windows, and run the installation program again. If the 
installation program still returns an error message after you exit and 
restart Windows, call FarPoint Technologies' Technical Support department 
at (919)460-1887 between the hours of 9:00 a.m. and 5:30 p.m. EST.  
  
  
**** Installed Files ****  
  
If you choose the default installation, the Tab Pro installation program  
copies the following files into your Windows system directory  
(for example, \WINDOWS\SYSTEM). The installation program also 
creates a \TABPRO20 directory on your hard disk and copies into it 
several subdirectories and files. The following table lists the files added 
to your Windows system directory and to the created directories.  
  
Directory	Files Installed	Description  
  
Your Windows	TABPRO.HLP	Help  
system directoryTABPRO.CNT	Help contents (Windows 95)  
  
\TABPRO20\	README.TXT	Read me file (This file)  
		UNWISE.EXE	Uninstall program  
		REDIST.TXT	List of files needed to redistribute Tab Pro
				controls
		UPGRAD.TXT	Instructions for upgrading existing projects from 
				Tab Pro version 1.1 or Tab/VBX version 1.1

\TABPRO20\BIN	IMP16D20.DLL	Imprint 16-bit DLL 
control  
		IMP32D20.DLL	Imprint 32-bit DLL control  
		IMP16X20.OCX	Imprint 16-bit OCX control  
		IMP32X20.OCX	Imprint 32-bit OCX control  
		IMPPRO20.VBX	Imprint VBX control  
		TAB16D20.DLL	Tab 16-bit DLL control  
		TAB32D20.DLL	Tab 32-bit DLL control  
		TAB16X20.OCX	Tab 16-bit OCX control  
		TAB32X20.OCX	Tab 32-bit OCX control  
		TABPRO20.VBX	Tab VBX control  
  
\TABPRO20\INCLUDE 
		TABPRO.BAS	Constants for Visual Basic  
		TABVBMFC.H	Header file for MFC (VBX)  
		TABVBOWL.H	Header file for OWL (VBX)  
		TABPRO.H	C function prototypes  
		TABDLL.H	C constant definitions  
		TABPMFC.CPP	C++ implementation  
		TABPMFC.H	C++ declarations for MFC users  
		TABPOWL.H	C++ declarations for OWL users  
  
\TABPRO20\LIB  
		IMP16D20.LIB	Imprint control DLL import library (16-bit)  
		TAB16D20.LIB	Tab control DLL import library (16-bit)  
		IMP32D20.LIB	Imprint control DLL import library (32-bit)  
		TAB32D20.LIB	Tab control DLL import library (32-bit)  
  
\TABPRO20\SAMPLES\		This directory contains sample   
				applications for different   
				development environments.  
  
The TABPRO.BAS file contains function prototypes for multiple 
environments. You must remove the comment characters for your 
development environment and control type.  
  
  
**** Upgrading Existing Tab Pro Version 1.1 Projects ****  
  
If you have created applications using Tab Pro version 1.1, you must  
upgrade your existing projects. Complete the steps provided for your  
development environment.  
  
Upgrading Visual Basic® Projects to Use the VBX Controls  
  
If you formerly used Tab Pro version 1.1 VBX controls and now want to use 
version 2.0 VBX controls, complete the following steps.  
  
To upgrade existing Visual Basic projects for VBX controls  
  
1. Open your existing project.  
2. If the project used the file TABPRO11.BAS,use the file TABPRO.BAS
   in place of it.
3. Save the project file and form files as text.  
4. Edit the project file (.MAK) to change the following references:  
	Change . . .	To . . .  
	IMPPRO11.VBX	IMPPRO20.VBX  
	TABPRO11.VBX	TABPRO20.VBX  
5. Edit the form files (.FRM) to change all TabPro and ImprintPro class  
   references as follows:  
	Change . . .		To . . .  
	fpVBImprintPro11	vaImprint  
	fpVBTabPro11		vaTabPro  
6. Load your project and verify your changes.  
  
Upgrading Visual Basic Projects to Use the OCX Controls  
  
If you formerly used Tab Pro version 1.1 VBX controls and now want to 
use version 2.0 OCX controls, complete the following steps.  
  
To upgrade existing Visual Basic projects for OCX controls  
  
1. Open your existing project.  
2. If the project used the file TABPRO11.BAS, use the file TABPRO.BAS
   in place of it.
3. Save the project file and form files as text.  
4. Edit the project file (.MAK) to change the following references:  
	Change . . .	To . . .  
	IMPPRO11.VBX	IMPPRO20.VBX  
	TABPRO11.VBX	TABPRO20.VBX  
5. Edit the form files (.FRM) to change all TabPro and ImprintPro class  
   references as follows:  
	Change . . .		To . . .  
	fpVBImprintPro11	vaImprint  
	fpVBTabPro11		vaTabPro  
6. Load your project and verify your changes.  
7. Save the project to rewrite the binary data in the .FRX file.  
8. Start Visual Basic 4.0 (16-bit) or Visual Basic 4.0 (32-bit) and load 
   the project file (.MAK).  
  
Upgrading C++ Projects to Use the VBX Controls  
  
If you formerly used Tab Pro version 1.1 VBX controls and now want to 
use version 2.0 VBX controls, complete the following steps.  
  
To upgrade existing C++ projects for VBX controls  
1. Open your existing project.  
2. If the project used the file TABDLL11.H, use the file TABDLL.H. 
   in place of it. If the project used the file TABPRO11.H, use the file
   TABPRO.H in place of it.  
3. If you used AppStudio to put a Tab control on a dialog, open the  
   .RC file as text in a text editor and make the following changes:  
	Change:	CONTROL "IMPPRO11.VBX;fpVBImprintPro11;	 
	To: 	CONTROL "IMPPRO20.VBX;vaImprint;  

	Change:	CONTROL "TABPRO11.VBX;fpVBTabPro11; 
	To: 	CONTROL "TABPRO20.VBX;vaTabPro; 
4. Rebuild your project and run it.  
  
Upgrading C or C++ Projects to Use the 16-Bit DLL Controls  
  
If you formerly used Tab Pro version 1.1 DLL controls and now want to 
use version 2.0 16-bit DLL controls, complete the following steps.  
  
To upgrade existing C or C++ projects for 16-Bit DLL controls  
1. Open your existing project.  
2. If the project used the file TABDLL11.H, change the filename to 
   TABDLL.H.  
3. If you hard coded the class name of the Imprint or Tab control in  
   your project, make the following changes:  
	a. Either use the define (FPCLASS_IMPRINT for Imprint or
	   FPCLASS_TAB for Tab) or  
	b. Make the following changes as needed:  
		Change . . .	To . . .  
		fpImprintPro11	fpImprintPro1620 (16-bit DLL)  
		fpTabPro11	fpTabPro1620 (16-bit DLL)  
4. Rebuild your project and run it.  
  
Note  To find the class names for 16- or 32-bit controls, search for the  
      define FPCLASS_IMPRINT or FPCLASS_TAB in the TABDLL.H file.  
 

**** Upgrading Existing Tab/VBX Version 1.1 Projects ****

If you have created applications using Tab/VBX version 1.1, you must 
upgrade your existing projects. Complete the steps provided for your 
development environment.

Upgrading Visual Basic Projects to Use the VBX Controls

If you formerly used Tab/VBX version 1.1 controls and now want to use 
Tab Pro version 2.0 VBX controls, complete the following steps.

To upgrade existing Visual Basic projects for VBX controls
1. Open your existing project.
2. If the project used the file TABVBX11.BAS, use the file TABPRO.BAS
   in place of it.
3. Save the project file and form files as text.
4. Edit the project file (.MAK) to change the following references:
	Change . . .	To . . .
	FPIMPRNT.VBX	IMPPRO20.VBX
	FPTAB11.VBX	TABPRO20.VBX
5. Edit the form files (.FRM) to change all Tab/VBX class references 
   as follows:
	Change . . .	To . . .
	fpVbImprint	vaImprint
	TabCtl		vaTabPro
6. Load your project and verify your changes.

Upgrading Visual Basic Projects to Use the OCX Controls

If you formerly used Tab/VBX version 1.1 controls and now want to use 
version Tab Pro version 2.0 OCX controls, complete the following steps.

To upgrade existing Visual Basic projects for OCX controls
1. Open your existing project.
2. If the project used the file TABVBX11.BAS, use the file TABPRO.BAS
   in place of it.
3. Save the project file and form files as text.
4. Edit the project file (.MAK) to change the following references:
	Change . . .	To . . .
	FPIMPRNT.VBX	IMPPRO20.VBX
	FPTAB11.VBX	TABPRO20.VBX
5. Edit the form files (.FRM) to change all Tab/VBX class references 
   as follows:
	Change . . .	To . . .
	fpVbImprint	vaImprint
	TabCtl		vaTabPro
6. Load your project and verify your changes.
7. Save the project to rewrite the binary data in the .FRX file.
8. Start Visual Basic 4.0 (16-bit) or Visual Basic 4.0 (32-bit) and 
   load the project file (.MAK).

Upgrading C++ Projects to Use the VBX Controls

If you formerly used Tab/VBX version 1.1 controls and now want to use 
Tab Pro version 2.0 VBX controls, complete the following steps.

To upgrade existing C++ projects for VBX controls
1. Open your existing project.
2. If the project used the file TABVBX11.H, use the file TABVBX.H
   in place of it.
3. If you used AppStudio to put a Tab control on a dialog, open the .RC 
   file as text in a text editor and make the following changes:
	Change:	CONTROL "FPIMPRNT.VBX;fpVbImprint;	 
	To: 	CONTROL "IMPPRO20.VBX;vaImprint;  

	Change:	CONTROL "FPTAB11.VBX;TabCtl; 
	To: 	CONTROL "TABPRO20.VBX;vaTabPro; 
4. Rebuild your project and run it.

 
**** Additional Information for C and C++ Users ****

If you are using Tab Pro controls in either C or C++, review the 
following information about using the controls.

====================================================================
Using Tab Pro Version 2.0 32-Bit DLL Controls in Borland C

To use Tab Pro version 2.0 32-bit DLL controls in Borland C, 
you must use version 5.0 or greater of Borland C's IMPLIB.EXE 
to generate a valid TAB32D20.LIB or IMP32D20.LIB. The IMPLIB 
command does not generate a backward-compatible library for 
earlier versions of Borland C (that is, for versions previous 
to version 5.0).

====================================================================
Using Tab Pro Version 2.0 32-Bit OCX Controls in MSVC 4.0

To use Tab Pro version 2.0 32-Bit OCX controls in MSVC 4.0,
you must generate wrapper classes for the controls.

To generate a wrapper class, you must use an existing application
that supports OLE controls, or you must create such an application.

Complete the steps in the following section to create an application
that supports OLE controls. If you already have such an application, 
proceed to the section "Generating a C++ Wrapper for Tab Pro Controls
in MSVC 4.0."
------------------------------------------------------------
Creating a New Application That Supports OLE Controls

To generate a new application that supports OLE controls

1. In MSVC 4.0, choose New from the File menu.
2. In the New dialog box, select Project Workspace from the New list.
3. Choose the OK button.
4. In the New Project Workspace dialog box,
   a. Select the default item (MFC AppWizard (exe)) from the Type list.
   b. Type a project name into the Name box.
   c. Type a location for your project files in the Location box
      or choose the Browse button to select a drive and directory.
   d. Choose the Create button.
5. In the MFC AppWizard - Step 1 dialog box, choose the Next button.
6. In the MFC AppWizard - Step 2 of 6 dialog box, choose the Next 
   button.
7. In the MFC AppWizard - Step 3 of 6 dialog box, select the OLE 
   controls check box and choose the Finish button. 
   This accepts the defaults for all other choices.
8. In the New Project Information dialog box, choose the OK button 
   and MSVC 4.0 generates an application that supports OLE controls.

------------------------------------------------------------
Generating a C++ Wrapper for Tab Pro Controls in MSVC 4.0

There are two methods for generating C++ wrappers in MSVC 4.0.
You can place the control on a dialog, or you can add the control
as an application component.


To generate a C++ wrapper with the control on a dialog

1.  Open an existing dialog or create a new dialog in MSVC 4.0.
    To create a new dialog, select Resource from the Insert menu. 
    Then, in the Insert Resource dialog box, select Dialog from the 
    Resource type list, and then choose the OK button.
2.  Click the right mouse button in the dialog to display the pop-up 
    menu.
3.  Choose Insert OLE Control.
4.  In the Insert OLE Control dialog box, select either FarPoint TabPro 
    Control or FarPoint ImprintPro Control from the OLE control list.
5.  Choose the OK button.
6.  Click the right mouse button in the dialog to display the pop-up 
    menu.
7.  Choose ClassWizard.
8.  If you are creating a new dialog, create a C++ class for the dialog 
    using the following steps:
    a. In the Adding a Class dialog box, choose the OK button.
    b. In the Create New Class dialog box under Class Information, type
       the new name in the Name box.
    c. Choose the Create button.
9.  Create a member variable for the control you inserted into your
    dialog using the following steps:
    a. In the MFC ClassWizard window on the Member Variables tab, 
       select the control ID of the OLE control you added to the dialog 
       from the Control IDs list.
    b. Choose the Add Variable button.
    c. Choose the OK button in the Microsoft Developer Studio message 
       that explains that a class wrapper will be generated for you.
10. In the Confirm Classes dialog box, you can modify the class name, 
    implementation filename, and the declaration header filename or 
    accept the defaults provided.
11. Choose the OK button.
12. In the Add Member Variable dialog box, type a variable name in the 
    Member variable name box.
13. Choose the OK button.
    ClassWizard generates a wrapper class to support the selected 
    Tab Pro 2.0 control.

 
To generate a C++ wrapper with the control as an application component

1. In MSVC 4.0, choose Component from the Insert menu.
2. In the Component Gallery dialog box, choose the OLE Controls tab.
3. Select either FarPoint TabPro Control or FarPoint ImprintPro Control 
   from the list.
4. Choose the Insert button.
5. In the Confirm Classes dialog box, you can modify the class name, 
   implementation filename, and the declaration header filename or 
   accept the defaults provided.
6. Choose the OK button.
7. In the Component Gallery dialog box, choose the Close button.
   ClassWizard generates a wrapper class to support the selected 
   Tab Pro 2.0 control.


**** Corrections to the User's Guide ****  
  
p. 16-18  
The following items should not be listed in the table of DLL functions:  
TabGetFlipText  
TabGetRotateText90  
TabGetStyle  
TabSetFlipText  
TabSetRotateText90  
  
p. 20  
The following item was inadvertantly omitted from the table of OCX/VBX  
properties:  
Tab  
  
  
**** Corrections to the Reference Guide ****  
  
p. 4  
The Action property description should read:  
"Sets a value that designates an action such as moving or clearing a  
specified tab. This property is available at run time only."  
  
p.17  
The example reference for the AlignTextV property should read:  
"Refer to the AllowScroll property example."  
  
p.19  
The C code for the AllowScroll property example should read:  
  
TabSetTabHeight(hWndTab, 20);   
TabSetTabMaxWidth(hWndTab, 300);   
TabSetTabCount(hWndTab, 7);   
TabSetAllowScroll(hWndTab, TAB_SCROLL_WHOLE);   
/* light gray, RGB(192, 192, 192) */   
TabSetEarMarkColorLight(hWndTab, 0x00C0C0C0);   
/* white, RGB(255, 255, 255) */   
TabSetEarMarkColorDark(hWndTab, 0x00FFFFFF);   
/* black, RGB(0, 0, 0) */   
TabSetEarMarkColorOutline(hWndTab, 0x00000000);   
TabSetEarMarkHeight(hWndTab, 17);   
TabSetAlignTextH(hWndTab, TAB_ALIGNTEXT_H_CENTER);   
TabSetAlignTextV(hWndTab, TAB_ALIGNTEXT_V_CENTER);  
  
p.19-20  
The C++ code for the AllowScroll property example should read:  
  
Tab1->SetTabHeight(20);   
Tab1->SetTabMaxWidth(300);   
Tab1->SetTabCount(7);   
Tab1->SetAllowScroll(TAB_SCROLL_WHOLE);   
// light gray, RGB(192, 192, 192)   
Tab1->SetEarMarkColorLight(0x00C0C0C0);   
// white, RGB(255, 255, 255)   
Tab1->SetEarMarkColorDark(0x00FFFFFF);   
// black, RGB(0, 0, 0)   
Tab1->SetEarMarkColorOutline(0x00000000);   
Tab1->SetEarMarkHeight(17);   
Tab1->SetAlignTextH(TAB_ALIGNTEXT_H_CENTER);   
Tab1->SetAlignTextV(TAB_ALIGNTEXT_V_CENTER);  
  
p.42-43  
The C code for the BookCreaseColor property example should read:  
  
TabSetMode(hWndTab, TAB_MODE_BOOK_TWOPAGES);   
TabSetOrientation(hWndTab, TAB_ORIENTATION_RIGHT);   
TabSetBookMarginH(hWndTab, 21);   
TabSetBookMarginV(hWndTab, 17);   
/* white, RGB(255, 255, 255) */   
TabSetBookCreaseColor(hWndTab, 0x00FFFFFF);   
TabSetBookCreaseType(hWndTab, TAB_BOOK_CREASETYPE_2LINES); 
TabSetBookShowMetalSpine(hWndTab, FALSE);   
TabSetBookRingShowHole(hWndTab, FALSE);   
TabSetBookRingCount(hWndTab, 2);   
TabSetBookRingGroupCount(hWndTab, 2);   
TabSetBookRingLength(hWndTab, 42);   
TabSetBookRingType(hWndTab, TAB_BOOK_RINGTYPE_DOUBLEWIRE);  
  
p.82  
The description for the ClipControls property should read:  
"Sets or returns whether display changes for the control cause the  
entire control to be refreshed (repainted) or just the newly exposed  
area. This property also determines whether the Windows environment  
creates a clipping region that excludes nongraphic controls contained  
within the control. This property is read only at run time."  
  
p.85
Remove the following paragraph:
"Inspect the value of the DataChanged property in your code for the 
Imprint control's Change event to avoid a cascading event. This applies 
to both bound and nonbound controls."

p. 91  
The description for the DrawFocusRect property should read:  
"Sets or returns whether and how the focus rectangle is displayed  
around the contents of the tab header."  
  
p.128-29  
The C code for the Mode property Example 3 should read:  
  
TabSetThreeDAppearance(hWndTab, 
TAB_THREEDAPPEARANCE_WINDOWS);  
TabSetOrientation(hWndTab, TAB_ORIENTATION_RIGHT);  
TabSetMode(hWndTab, TAB_MODE_BOOK_TWOPAGES);  
/* blue, RGB(0, 0, 255) */  
TabSetOutlineColor(hWndTab, 0x00FF0000);  
/* white, RGB(255, 255, 255) */  
TabSetGrayAreaColor(hWndTab, 0x00FFFFFF);  
/* dark gray, RGB(128, 128, 128) */  
TabSetBackColor(hWndTab, 0x00808080);  
/* light gray, RGB(192, 192, 192) */  
TabSetBookColor(hWndTab, 0x00C0C0C0);  
TabSetBookCornerWidth(hWndTab, 16);  
TabSetBookCornerHeight (hWndTab, 16);  
TabSetBookCornerType(hWndTab, 
TAB_BOOK_CORNERTYPE_CHAMFERED);  
TabSetBookRingLength(hWndTab, 58);  
/* second tab */  
TabSetTab(hWndTab, 1);  
TabSetPageMax(hWndTab, 5);  
/* white, RGB(255, 255, 255) */  
TabSetPageColor(hWndTab, 0x00FFFFFF);  
/* make second tab active */  
TabSetActiveTab(hWndTab, 1);  
/* make third page active */  
TabSetActivePage(hWndTab, 2);  
  
p.129  
The C++ code for the Mode property Example 3 should read:  
  
Tab1->SetThreeDAppearance(TAB_THREEDAPPEARANCE_WINDOWS);  
Tab1->SetOrientation(TAB_ORIENTATION_RIGHT);  
Tab1->SetMode(TAB_MODE_BOOK_TWOPAGES);  
// blue, RGB(0, 0, 255)  
Tab1->SetOutlineColor(0x00FF0000);  
// white, RGB(255, 255, 255)  
Tab1->SetGrayAreaColor(0x00FFFFFF);  
// dark gray, RGB(128, 128, 128)  
Tab1->SetBackColor(0x00808080);  
// light gray, RGB(192, 192, 192)  
Tab1->SetBookColor(0x00C0C0C0);  
Tab1->SetBookCornerWidth(16);  
Tab1->SetBookCornerHeight(16);  
Tab1->SetBookCornerType(TAB_BOOK_CORNERTYPE_CHAMFERED);  
Tab1->SetBookRingLength(58);  
// second tab  
Tab1->SetTab(1);  
Tab1->SetPageMax(5);  
// white, RGB(255, 255, 255)  
Tab1->SetPageColor(0x00FFFFFF);  
// make second tab active  
Tab1->SetActiveTab(1);  
// make third page active  
Tab1->SetActivePage(2);  
  
p.132
The constant for the MousePointer property, setting 9 (Size WE) 
for VB4 is incorrect. The correct constant is vbSizeEW.

p.173  
The constants for the TabShapeApplyTo property should be:  
0 - Both Corners	TAB_TABSHAPEAPPLYTO_BOTH  
1 - Left Corner		TAB_TABSHAPEAPPLYTO_LEFT  
2 - Right Corner	TAB_TABSHAPEAPPLYTO_RIGHT  
  
The example code for the TabShapeApplyTo property should read:  
C  
TabSetTabCount(hWndTab, 8);  
TabSetTabShapeApplyTo(hWndTab, TAB_TABSHAPEAPPLYTO_LEFT);  
TabSetTabShape(hWndTab, TAB_SHAPE_ROUNDED);  
C++  
Tab1->SetTabCount(8);  
Tab1->SetTabShapeApplyTo(TAB_TABSHAPEAPPLYTO_LEFT);  
Tab1->SetTabShape(TAB_SHAPE_ROUNDED);  
Visual Basic  
Tab1.TabCount = 8  
Tab1.TabShapeApplyTo = TAB_TABSHAPEAPPLYTO_LEFT  
Tab1.TabShape = TAB_SHAPE_ROUNDED  
  
p.232  
The example code for the TabSetActiveTabPage function should read:  
  
Ret = TabSetActiveTabPage Tab1.hWnd, 1, 3  
  
p.235-36  
The following Imprint control styles were inadvertently omitted:  
 
  IMPSX_BORDERTEXTFLIP 
	Flips border text 180 degrees	0x2000L  
 
 The following three styles are mutually exclusive:  
  IMPSX_BORDERORIENTBOTTOM 
	Orients border text on bottom of border 
	0x0800L  
  IMPSX_BORDERORIENTLEFT 
	Orients border text on left side of border 
	0x1000L  
  IMPSX_BORDERORIENTRIGHT 
	Orients border text on right side of border 
	0x0400L  
 
 The following two styles are mutually exclusive:  
  IMPSX_BORDERTEXTRIGHT 
	Right aligns border text	0x0200L  
  IMPSX_BORDERTEXTCENTER 
	Centers the border text horizontally 
	0x0100L  
  
  
**** Contacting FarPoint Technologies, Inc. ****  
  
If you discover a problem with either the software or the accompanying  
documentation, or if you would like to share your thoughts about this  
product with FarPoint Technologies, please send us a completed  
Comment Form.  
  
Send us the Comment Form using one of the following methods, or if you  
call, please provide the information requested on the form to our  
technical support representative. For additional assistance, contact our  
Technical Support department.  
  
To contact FarPoint Technologies, Inc.  
  
- Call our Technical Support department at (919) 460-1887.   
  FarPoint Technologies' Technical Support department is available  
  between the hours of 9:00 a.m. and 5:30 p.m. EST.  
  
- Fax us at (919) 460-7606.  
  
- Post comments or questions to the Technical Support forum on our  
  Bulletin Board Service at (919) 460-6712 (28.8K bps) or  
  (919) 460-5771 (1200 to 14.4K bps).  
  
- Contact the FarPoint forum on CompuServe (type GO FARPOINT).  
  
- Write us at:  
   FarPoint Technologies, Inc.  
   133 Southcenter Court  
   Suite 1000  
   Morrisville, NC 27560  
  
- Send e-mail to us at farpoint@fpoint.com (general mail) or 
  fpsupport@fpoint.com (technical support).  
  
You can also contact FarPoint Technologies at  
  
- Our World Wide Web site (http://www.fpoint.com/fpoint)  
  
- Our FTP site (ftp.fpoint.com and change to the directory /pub/fpoint)  
  
  
**** Tab Pro Comment Form ****  
  
If you encounter a problem with this product, or if you would like to share  
your comments with FarPoint Technologies, please complete and send this  
form to FarPoint Technologies.  
  
If you are reporting a problem, please include a detailed description of  
the problem along with the steps necessary to reproduce it. The preferred  
method is a sample application that reproduces the problem. If you have a  
sample, please upload it to our BBS at (919) 460-6712 (28.8K bps) or  
(919) 460-5771 (1200 to 14.4K bps), to our CompuServe forum (GO 
FARPOINT), or to our Internet address (fpsupport@fpoint.com or FTP to 
ftp.fpoint.com and change to the directory /pub/fpoint/upload). Be sure to 
include the name of the *.ZIP file that you uploaded.  
  
Today's date: ______________ 
 
Customer name: ______________________  
 
Company name: __________________ 
 
Phone number: (_____)_________________  
 
Fax number: (_____)____________________ 
 
E-mail address: __________________________  
 
*Sample application file name: ________________  
  
Control or controls used in application (circle one or both): 
	Imprint		Tab  
 
Version Number: 2.0		Control Date: _________________  
  
Control Type (circle one or more): 
	16-bit DLL    32-bit DLL    VBX    16-bit OCX    32-bit OCX  
 
Development environment: ____________________	Version: ______  
(for example, Visual Basic, Visual C++, Borland C++)  
  
Description of the problem:  
  
  
  
Steps necessary to reproduce the problem:  
  
  
  
Comments/Documentation suggestions:  
  
  
  

© 1996 FarPoint Technologies, Inc.