Register
Login
Hide

SftMask/OCX 7.0 - ActiveX Masked Edit Control

Display
Print

Upgrading to Version 7.0

Converting an Existing Application

The conversion is not automatic, but takes just a few minutes for a project.

Only a minimal conversion is required when upgrading to SftMask/OCX 7.0. SftMask/OCX 7.0 is virtually 100% source compatible with older releases of SftMask/OCX and SftMask/ATL. Your application(s) must be recompiled to use SftMask/OCX 7.0. SftMask/OCX 7.0 and an older version of SftMask/OCX (and SftMask/ATL) can coexist on the same system (both can be installed and used at the same time) and they can be used in the same application.

Make sure to back up your current projects, before converting your projects. Please read the conversion process specific to your language carefully BEFORE converting your project. After converting, once the control saves updated property settings, you will not be able to return to SftMask/OCX 6.5.

Visual Basic
.NET (Managed Languages)
Visual C++ (Unmanaged C/C++)
HTML
Other Development Tools

Visual Basic

After installing SftMask/OCX 7.0, all your projects will continue to use SftMask/OCX 6.5 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 (VPB File):

Type=Exe
Form=Form1.frm
Reference=*\G{00020430-0000-0000-C000-000000000046}#2.0#0#G:\WINNT\System32\stdole2.tlb#OLE Automation
Object={5F2D1CA0-5580-4d70-8B3A-228A2C660BB9}#6.5#0; SftMask_IX86_U_65.OCX
IconForm="Form1"
Startup="Form1"
ExeName32="yourexe.exe"
Command32=""
Name="yourproject"

The line describing SftMask/OCX 6.5 (above, using a bold font) should be replaced with the following line:

Object={3BB14700-AC40-4737-B5A6-920366D254FE}#7.0#0; SftMask_IX86_U_70.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 SftMask/OCX product directory. The line must be copied as-is, without any modifications.

Existing Forms And Modules (FRM, BAS Files):

All forms and modules must be edited using a text editor. The following changes can easily be accomplished by a global edit and replace operation:

All references to "SftMaskLib65" must be replaced by "SftMaskLib70".

All references to "SftMaskLib." must be replaced by "SftMaskLib70.". Make sure to include the trailing period in both cases. "SftMaskLib." is only used if you are upgrading from a release older than SftMask/OCX 6.0.

Once the VBP and FRM file have been saved, you can open the project in Visual Basic. Make sure to review each form (in design mode) and save it to complete the upgrade. The controls will save updated property settings, so you will not be able to return to SftMask/OCX 6.5. Once all forms have been saved, the project is using SftMask/OCX 7.0.

.NET (Managed Languages)

While most other languages offer a fairly easy conversion, .NET and its languages require a bit more effort, but in most cases is limited to the steps documented below.

Existing Forms (FRM Files):

Updating the forms to use SftMask/OCX 7.0 is quite straightforward:

  • A reference to SftMask/OCX 7.0 needs to be added to the project. This is easily accomplished by adding a SftMask/OCX 7.0 control to any form of your project. It is located in the toolbox group Softel vdm, Inc. For information about this, please see "Using SftMask/OCX with .NET". As soon as this new control is added to your form, the references are added to your project. The Solution Explorer window now shows two new references to AxSftMaskLib70 and SftMaskLib70. Once these references are added, the new control can be deleted from your form. The references remain.
  • Add the SftHelperComponent component to your form. It is located in the toolbox group Softel vdm, Inc. For information about this, please see "Using SftMask/OCX with .NET (C#, VB.NET)". The SftHelperComponent component eliminates the need for the OLEConvert.cs or OLEConvert.vb source files that were used in earlier releases.
  • Close all forms.
  • Open each form, one at a time, using the View Code menu entry in the Solution Explorer window. The popup menu is accessed by right-clicking on a form name. If you accidentally open a form in design mode, close it without saving, as your current control settings for this form are most likely lost.
    • Edit all occurrences of "SftMaskLib65" and replace them with "SftMaskLib70"
    • Edit all occurrences of "SftMaskLib." and replace them with "SftMaskLib70.". Make sure to include the trailing period in both cases. "SftMaskLib." is only used if you are upgrading from a release older than SftMask/OCX 6.0.
    • C#: Edit all occurrences of using OLEConvert; and replace them with using Softelvdm.OLEConvert;
    • VB: Edit all occurrences of Imports projectname.OLEConvert and replace them with Imports Softelvdm.OLEConvert
  • The existing references to SftMask/OCX 6.5 (or older) can now be removed. If the Solution Explorer window shows references to AxSftMaskLib65 and SftMaskLib65, these can be removed.
  • If your project includes the source file OLEConvert.cs (C#) or OLEConvert.vb (VB), remove it now. It is no longer needed.

The forms can now be opened and the project uses SftMask/OCX 7.0 exclusively. You will not be able to return to SftMask/OCX 6.5.

Visual C++ (Unmanaged C/C++)

Resource Script

After installing SftMask/OCX 7.0, all your projects will continue to use SftMask/OCX 6.5 until you make the following change in each dialog resource that defines a SftMask/OCX control. Before opening the resource script (RC file), make sure to close the project in Visual C++, then edit the RC file using a text editor and make the following changes:

IDD_MFC_DIALOG DIALOGEX 0, 0, 320, 200
STYLE DS_MODALFRAME | WS_POPUP | WS_VISIBLE | WS_CAPTION | WS_SYSMENU
EXSTYLE WS_EX_APPWINDOW
CAPTION "MFC"
FONT 8, "MS Sans Serif"
BEGIN
 DEFPUSHBUTTON "OK",IDOK,260,7,50,14
 PUSHBUTTON "Cancel",IDCANCEL,260,23,50,14
 CONTROL "",IDC_SFTMASKPHONE,
"{5F2D1CA4-5580-4d70-8B3A-228A2C660BB9}",WS_TABSTOP,7,33,
 121,12
END

The contents of the line describing SftMask/OCX 6.5 (above, using a bold font) should be replaced with the following line:

 CONTROL "",IDC_SFTMASKPHONE,
 "{3BB14704-AC40-4737-B5A6-920366D254FE}",WS_TABSTOP,7,33,
 121,12

Only change the ClassID (i.e., 5F2D1CA4-5580-4d70-8B3A-228A2C660BB9 to 3BB14704-AC40-4737-B5A6-920366D254FE), do not change the rest of the line.

You can copy this information directly from this help file or copy it from the file "Upgrade.txt" which you can find in the SftMask/OCX product directory. The ClassID must be copied as-is, without any modifications.

Once the RC file has been saved, you can open the project in Visual C++ and the project is now using SftMask/OCX 7.0. The controls will save updated property settings, so you will not be able to return to SftMask/OCX 6.5.

Make sure to change ALL occurrences of SftMask/OCX to version 6.5, otherwise you will not be able to open the resource script (RC file).

#import Statements

Any #import statements that are used in your application must now use the new control:

#import <msdatsrc.tlb> no_namespace

#pragma warning(disable : 4192) // automatically excluding 'Ixxx' while importing type library 'stdole2.tlb'
// For information about the following construct, please see Microsoft's
// KnowledgeBase entry Q224610
#import <SftMask_IX86_U_65.ocx> rename_namespace("SftMaskNameSpace")
#if _MSC_VER >= 1400 // need at least Visual Studio 2005
# pragma comment(lib, "comsuppw.lib") // avoid link error in VS2005
#endif
#pragma warning(default : 4192)

using namespace SftMaskNameSpace;

should be replaced with

#import <msdatsrc.tlb> no_namespace

#pragma warning(disable : 4192) // automatically excluding 'Ixxx' while importing type library 'stdole2.tlb'
// For information about the following construct, please see Microsoft's
// KnowledgeBase entry Q224610
#import <SftMask_IX86_U_70.ocx> rename_namespace("SftMaskNameSpace") rename("LoadImage", "LoadImageSftMask")
#if _MSC_VER >= 1400 // need at least Visual Studio 2005
# pragma comment(lib, "comsuppw.lib") // avoid link error in VS2005
#endif
#pragma warning(default : 4192)

using namespace SftMaskNameSpace;

HTML

After installing SftMask/OCX 7.0, all your HTML pages will continue to use SftMask/OCX 6.5 until you make the following change in each page that uses a SftMask/OCX control.

<OBJECT ID="Mask1" WIDTH=708 HEIGHT=203
 CLASSID="CLSID:5F2D1CAE-5580-4d70-8B3A-228A2C660BB9"
 CODEBASE="SftMask_IX86_I_65.cab#version=6,5,0,0">
 <PARAM NAME="_Version" VALUE="262144">
 <PARAM NAME="_ExtentX" VALUE="14993">

The contents of the line describing SftMask/OCX 6.5 (above, using a bold font) should be replaced with the following:

 CLASSID="CLSID:3BB1470E-AC40-4737-B5A6-920366D254FE"
 CODEBASE="SftMask_IX86_I_70.cab#version=7,0,0,0">

Only change the ClassID (i.e., "5F2D1CAE-5580-4d70-8B3A-228A2C660BB9" to "3BB1470E-AC40-4737-B5A6-920366D254FE"), do not change the rest of the line.

The CODEBASE argument also needs to be updated to reflect the new cabinet name and the current version number.

You can copy this information directly from this help file or copy it from the file "Upgrade.txt" which you can find in the SftMask/OCX product directory. The ClassID must be copied as-is, without any modifications.

Once the page has been saved, you can open the web page using your preferred HTML editor. The controls will save updated property settings, so you will not be able to return to SftMask/OCX 6.5.

Other Development Tools

Most development tools allow access to the ClassID used for controls on a form or dialog. Sometimes this may be accomplished by using a text editor and editing a configuration file, or possibly the development tool allows direct modification of the ClassID.

Generally, the ClassID used for the prior release 5F2D1CA0-5580-4d70-8B3A-228A2C660BB9 must be replaced with the new ClassID 3BB14700-AC40-4737-B5A6-920366D254FE. Once this step is completed, opening the project is sufficient to allow SftMask/OCX to convert the stored property settings.

For specific instructions or help, please see your development tool's documentation.

Last Updated 08/13/2020 - (email)
 © 2024 Softel vdm, Inc.