"Fossies" - the Fresh Open Source Software Archive

Member "vb/VBReadMe.txt" (25 Jan 2009, 2998 Bytes) of package /windows/misc/unz600dn.zip:

As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 On Windows, please read this file using WordPad to format lines properly.
    3 This directory contains a short example on how to use the Win32 UnZip DLL
    4 with Visual Basic.  The example code consists of a simple dialog form and
    5 a standard module containing the interface code to call unzip32.dll.
    6 The code assumes that the unzip32.dll binary is available somewhere on the
    7 execution path. The easiest way to satisfy this rule is to keep a copy of
    8 unzip32.dll in the directory where the VB executable is stored, but if
    9 it's in the command path it should be found.
   10 NOTE: Whenever a VB program is run from the VB6 IDE, the "path of the VB
   11 executable" is the path where the IDE program file "VB6.EXE" is stored,
   12 NOT the storage directory of the VB project file (= result of the App.Path
   13 property accessed from within the VB program).
   15 The example code has been edited last with Visual Basic 6, but should be
   16 compatible with VB 5. To maintain compatibility with VB5 after having modified
   17 the example project in VB6, the project file has to be edited using a standard
   18 text editor (e.g.: Notepad), to remove the line specifying the "Retained"
   19 property.  This property line is not recognized by VB 5 and would prevent
   20 correct loading of the project in VB 5.
   22 This VB example makes use of the "Windows Common Dialogs" ActiveX control
   23 comdlg32.ocx, supplied with Visual Basic. Unfortunately, there are different
   24 revisions of this control available which are not binary compatible. In order
   25 to maintain compatibility of the source code with all available versions of
   26 comdlg32.ocx, the source files may have to be edited manually after the
   27 program has been saved from the VB environment on a system containing the
   28 latest release of comdlg32.ocx:
   30 Both vbunzip.frm and vbunzip.vbp should contain a reference line for the
   31 common dialog ocx reading like:
   32 Object = "{F9043C88-F6F2-101A-A3C9-08002B2F49FB}#1.1#0"; "COMDLG32.OCX"
   33                                                  ^^^
   34 The important section of this line is the revision number "1.1" (marked by
   35 the "^^^" signs). On a system with a more recent version of comdlg32.ocx
   36 installed, this version number is updated to "1.2" (or higher) by VB
   37 automatically. This number has to be changed back to "1.1" manually,
   38 otherwise the example code can no longer be used on systems with old versions
   39 of comdlg32.ocx.
   41 When fetching the VB example code from the UnZip source distribution, one
   42 has to make sure that the files are stored in the correct "DOS/Windows-native"
   43 text format with "CR-LF" line endings. Visual Basic does not accept Unix style
   44 text format (LF line terminators) for Form class modules (*.frm) and the
   45 project file (*.vbp).  You may use unzip's -a option to convert the project
   46 on extraction. If this is a full source distribution, see the Where file for
   47 where to download the compiled unzip DLL for a specific platform which includes
   48 this example project in native format for that platform.
   50 For more information, see the comments within the VB source.