When upgrading from 4.0 (or an older version), all steps shown in "Upgrading to Version 6.0" must be performed. In addition, these steps apply:

Converting an Existing Application

1. Current Tab

Starting with release 4.5, applications must explicitly define an active tab (see SetCurrentTab), otherwise no tab will be activated.

C applications should set the current tab immediately after initializing the tab control using SetControlInfo.

C++/ MFC applications typically do not need to be modified as the call to InitializeTabControl explicitly activates a tab.  Only applications that use a tab control without the page or sheet classes (which always use InitializeTabControl) will have to explicitly use SetCurrentTab.

2. SFTTABSN_SWITCHING and SFTTABSN_SWITCHED Notifications

The SFTTABSN_SWITCHING and SFTTABSN_SWITCHED notifications may now occur at unexpected times and must anticipate that no tab is active (GetCurrentTab returns -1). 

3. SFTTABS_CONTROL, New Members, Initialization

In order to use new features, SetVersion must be called with the new version indicator SFTTABS_6_0. Once the new version is activated in your source code, the new members found in the SFTTABS_CONTROL structure must be initialized. If SetVersion is called with an earlier version indicator, these fields need not be initialized. New tab control features will however not be available.

Member	Suggested Initialization Value
new in 4.5
hButtonBitmapDisabled	NULL
fShowFocusRectangle	TRUE
new in 5.0
fClosable	FALSE
fCloseDisabled	FALSE
fSendWMCLOSE	FALSE
fCloseFullSize	FALSE
buttonAlignment	0
closeButtonAlignment	0
fMinimizeButton	FALSE
fMinimizeDisabled	FALSE
fRestoreButton	FALSE
fRestoreDisabled	FALSE
hButtonBitmap2	NULL
hButtonBitmap2Disabled	NULL
szLeftToolTip	_T("")
szRightToolTip	_T("")
szCloseToolTip	_T("")
szMinimizeToolTip	_T("")
szRestoreToolTip	_T("")
nCustomCode	0

By using the suggested initialization values, the tab control will continue to operate as in earlier versions.

4. SFTTABS_TAB, New Members, Initialization

In order to use new features, SetVersion must be called with the new version indicator SFTTABS_5_0. Once the new version is activated in your source code, the new members found in all SFTTABS_TAB structures for the tab control must be initialized. If SetVersion is called with an earlier version indicator, these fields need not be initialized. New tab control features will however not be available.

 

Member	Suggested Initialization Value
new in 4.5
hImageList	NULL (This member has been moved from the SFTTABS_TAB_EX, see below)
fHidden	FALSE
new in 5.0
colorBgStart	SFTTABS_NOCOLOR
colorBgEnd	SFTTABS_NOCOLOR
colorBgSelStart	SFTTABS_NOCOLOR
colorBgSelEnd	SFTTABS_NOCOLOR
colorClientAreaStart	SFTTABS_NOCOLOR
colorClientAreaEnd	SFTTABS_NOCOLOR

By using the suggested initialization values, the tab control will continue to operate as in earlier versions.

5. SFTTABS_TAB_EX Dropped

The SFTTABS_TAB_EX structure has been discontinued and merged into the SFTTABS_TAB structure.

Applications making use of tab-specific Image List controls (SFTTABS_TAB_EX structure, hImageList member) must be modified to use the hImageList member of the SFTTABS_TAB structure instead. This conversion is quite straightforward and actually simplifies processing, because only one structure needs to be retrieved and updated. Applications using the control's Image List only (SFTTABS_CONTROL, hImageList member) do not need to be modified.