Upgrading to Version 6.5
Only a minimal conversion is required when upgrading from SftTabs/ATL 3.5, 4.0, 4.5, 5.0 or 6.0 to SftTabs/OCX 6.5. SftTabs/OCX 6.5 is source compatible with 3.5, 4.0, 4.5, 5.0 and 6.0 of SftTabs/ATL and SftTabs/OCX. Your application(s) must be recompiled to use SftTabs/OCX 6.5.
SftTabs/OCX 6.5 and older versions of SftTabs/ATL can coexist on the same system (both can be installed at the same time). They cannot be used in the same application.
In order to convert an application, both the older version and SftTabs/OCX 6.5 must be installed.
Converting an Existing Application
The conversion is not automatic. After installing SftTabs/OCX 6.5, all your projects will continue to use SftTabs/OCX 6.0 until you make the following change in each project's main VBP (Visual Basic Project) file. Before opening the project file, make sure to close the project in Visual Basic, then edit the VBP file using a text editor and make the following changes:
Existing Project:
Type=Exe
Form=Form1.frm
Reference=*\G{00020430-0000-0000-C000-000000000046}#2.0#0#G:\WINNT\System32\stdole2.tlb#OLE Automation
Object={D3267B1B-B7B2-422a-9661-43269988CF74}#6.0#0; SftTabs_IX86_U_60.ocx
IconForm="Form1"
Startup="Form1"
ExeName32="Features.exe"
Command32=""
Name="Project1" The line describing SftTabs/OCX 6.0 (using a bold font) should be replaced with the following line:
Object={919B661B-D0B2-4961-B128-D7C32DF3B10C}#6.5#0; SftTabs_IX86_U_65.ocx You can copy this line directly from this help file or copy it from the file "Upgrade.txt" which you can find in the SftTabs/OCX product directory. The line must be copied as-is, without any modifications.
Once the VBP file has been saved, you can open the project in Visual Basic and the project. As you open each form containing an old version of the control, it is converted to SftTabs/OCX 6.5. Each form must be opened and saved to complete the conversion.
The controls will save updated property settings, so you will not be able to return to SftTabs/OCX 6.0.
Conversion Issues
When upgrading from SftTabs/OCX 6.0 or earlier, the following applies:
- Applications that use Style = styleSftTabsButtonsTop (66) through styleSftTabsButtonsDualLeftRightV (74): In older versions, the UseClientAreaColors property was ignored when Windows themes where used. This is no longer the case. If you want the old behavior, make sure to set UseClientAreaColors to False.
- Applications that use Style = styleSftTabsButtonsTop (66) through styleSftTabsButtonsDualLeftRightV (74): The background around the tab buttons will use the true background colors when UseExactRegion (set to True) is used with Windows themes.
When upgrading from SftTabs/ATL 5.0, no changes must be made.
When upgrading from SftTabs/ATL 4.5, no changes must be made.
When upgrading from SftTabs/ATL 4.0 or earlier, the following applies:
- Applications that added all tabs at run-time will now have to explicitly activate at least one tab (see Tabs.Current). While SftTabs/ATL 4.0 automatically activated the first tab, this is no longer the case.
On
Off