Upgrading to Version 7.5
Only a minimal conversion is required when upgrading from an earlier version of SftTree/DLL to SftTree/DLL 7.5. SftTree/DLL 7.5 is virtually 100% source compatible with SftTree/DLL 7.0. Your application(s) must be recompiled to use SftTree/DLL 7.5. Additional upgrade requirements exist when upgrading from SftTree/DLL 4.0 and older versions. Please see "Upgrading from SftTree/DLL 4.0" for more information.
SftTree/DLL 7.5 and older versions of SftTree/DLL can coexist in the same application to make the conversion as easy as possible, however, they cannot be used in the same source code file.
Windows 98 and Windows ME are no longer supported. For support of these platforms, an older version of SftTree/DLL must be used instead (version 6.0 or earlier).
Upgrading to Version 7.5
To allow for SftTree/DLL 7.5 to coexist with older versions on the same system, the Dlls have been renamed and a new window class is used.
SftTree/DLL 7.5 is source code compatible with older releases of SftTree/DLL, provided the following changes are made in existing applications:
Converting an Existing Application
The conversion effort to upgrade an application using SftTree/DLL 7.0 is very minimal. Most applications will only have to change the window class name used in DIALOG resources (see below).
Window Class Change
In SftTree/DLL 7.0 (the release prior to SftTree/DLL 7.5), the window class used for SftTree was SftTreeControl70 (SftTreeSplit70). These window classes have been dropped and have been renamed to SftTreeControl75 (SftTreeSplit75).
Any DIALOG resources that use the old window classes must be changed to use SftTreeControl75 and SftTreeSplit75. Without this change, the dialogs will not be displayed.
If the window class name was "hard-coded" in calls to CreateWindow(Ex), the class name must also be changed. The preferred method is to use the preprocessor symbol SFTTREE_CLASS (SFTTREESPLIT_CLASS).
Dll And Lib Files Name Change
The Dlls and Lib files have been renamed for this new release. For the new file names, please see the section "Building Applications".
When linking statically, the libraries Gdiplus.lib and Msimg32.lib must be added to the linker project settings (see the section "Building Applications").
On
Off