SftTree/DLL 7.5 - Tree Control
SftBox/OCX 5.0 - Combo Box Control
SftButton/OCX 3.0 - Button Control
SftMask/OCX 7.0 - Masked Edit Control
SftTabs/OCX 6.5 - Tab Control (VB6 only)
SftTree/OCX 7.5 - Tree Control
SftPrintPreview/DLL 2.0 - Print Preview Control (discontinued)
SftTree/DLL 7.5 - Tree Control
SftBox/OCX 5.0 - Combo Box Control
SftButton/OCX 3.0 - Button Control
SftDirectory 3.5 - File/Folder Control (discontinued)
SftMask/OCX 7.0 - Masked Edit Control
SftOptions 1.0 - Registry/INI Control (discontinued)
SftPrintPreview/OCX 1.0 - Print Preview Control (discontinued)
SftTabs/OCX 6.5 - Tab Control (VB6 only)
SftTree/OCX 7.5 - Tree Control
SftTabs/NET 6.0 - Tab Control (discontinued)
SftTree/NET 2.0 - Tree Control
Distributing the DLLs included with SftPrintPreview/DLL is only possible in accordance with the licensing agreement. The licensing agreement is furnished with the purchase of SftPrintPreview/DLL.
The DLLs contain your license number and are serialized.
Modification of the original DLLs as included with the product is not permitted to insure that no incompatibilities exist between different software packages that use SftPrintPreview/DLL. Any install procedure that is used to install DLLs which are included with SftPrintPreview/DLL must do proper version checking.
Applications you create with SftPrintPreview/DLL for distribution must be completed end-user application. It is not possible to distribute the controls to unlicensed users for development purposes. This means that your distributed end-user application cannot be a Debug build, cannot contain debug information, symbol information, etc.
The following DLLs can be distributed royalty-free with your application in accordance with the licensing agreement. The licensing agreement is furnished with the purchase of SftPrintPreview/DLL.
The application's executable (EXE or DLL) must be linked with the correct LIB file, depending on the target environment and the compiler used. The DLL must be available and accessible at run-time for proper execution. The DLL used at run-time depends on the LIB file used at link time.
Intel 32-Bit Processor | Intel IX86 | ||
---|---|---|---|
Operating System | All supported platforms 32-bit Applications using ANSI character representation | All supported platforms 32-bit Applications using UNICODE character representation | Windows 2000 and above - only 32-bit Applications using UNICODE character representation |
DLLs | SftPrintPreview_IX86_A_20.dll | SftPrintPreview_IX86_U_20.dll | SftPrintPreview_IX86_V_20.dll |
Unicows.dll (see Note 1) | (see Note 2) | ||
optional resource-only DLLs for National Language Support | optional resource-only DLLs for National Language Support | optional resource-only DLLs for National Language Support |
1) The UNICODE DLL SftPrintPreview_IX86_U_20.dll can be distributed for all platforms, even platforms that have very limited UNICODE support, such as Windows 95, 98, ME. On these platforms, the DLL Unicows.dll must also be distributed and is required for Windows 95, 98, ME. It can be installed on Windows 2000, XP and above, but is not used. The DLL Unicows.dll can only be distributed under license from Microsoft Corp. This DLL can be downloaded at no charge from Microsoft's web site at http://www.microsoft.com/downloads/ searching for product "Platform SDK". The title of the item is "Platform SDK Redistributable: MS Layer for Unicode on Windows 95/98/ME Systems".
2) The DLL SftPrintPreview_IX86_V_20.dll can be distributed for UNICODE-enabled platforms only. It is identical to SftPrintPreview_IX86_U_20.dll, but Unicows.dll is not required.
Intel 64-Bit Processor (with EM64T) AMD 64-Bit Processor | Intel and AMD 64-Bit Processors | |
---|---|---|
Operating System | Windows XP and above - 64-bit applications using ANSI character representation | Windows XP and above - 64-bit applications using UNICODE character representation |
DLLs | SftPrintPreview_x64_A_20.dll | SftPrintPreview_x64_U_20.dll |
optional resource-only DLLs for National Language Support | optional resource-only DLLs for National Language Support |
All required files can be found in the directory \Program Files\Softelvdm\SftPrintPreview DLL 2.0\Lib and \Program Files\Softelvdm\SftPrintPreview DLL 2.0\Dll, unless changed during the installation. On Windows 64-bit versions, the root folder is \Program Files (x86).
Please note that processor support depends on the installed and purchased product versions.
Certain features of the control require GDI+ support. This is available automatically on Windows XP and newer Windows versions. GDI+ is available as a redistributable for Windows 2000, Windows 98, and Windows Me from Microsoft (www.microsoft.com) as part of the Platform SDK (Windows XP and newer). Usually, it is sufficient to simply distribute the Dll gdiplus.dll in your application directory.
When using SFTPRINTPREVIEW_DRAWINFO, pGraphics to render output to a page, GDI+ support is required.
The DLLs can be installed in the application's directory and can be used locally, without interfering with any other applications which may use other versions of SftPrintPreview/DLL.
The DLLs included with SftPrintPreview/DLL can also be installed in the Windows SYSTEM directory. Under Windows 2000, XP, Server 2003, Vista, Server 2008, Windows 7 and Windows 7 Server the 32-bit DLLs are installed in the SYSTEM32 directory. Under 64-bit Windows versions, 64-bit DLLs are installed in the SYSTEM32 directory and the 32-bit DLLs are installed in the SYSWOW64 directory. When installing DLLs in Windows directories, strict version checking and reference counting must be performed to avoid conflicts if different software packages use SftPrintPreview/DLL.
Any resource-only DLLs for National Language Support must be installed in the application directory (never in the Windows System(32) directory).
The DLLs included with SftPrintPreview/DLL carry proper version information. A shared DLL should only be replaced if its version information indicates that the existing DLL is older.
Commercial installers and setup programs have built-in features to insure proper DLL versioning. See your installer's documentation for more information.
If a DLL is installed into the Windows System(32) or SysWOW64 directory directory, it can potentially be installed and used by other applications also. It is required that any DLL installed in such a shared location keep proper reference counts by updating the proper Windows registry keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs
Commercial installers and setup programs have built-in features to insure proper usage and reference counting. See your installer's documentation for more information.