CONTAINER VBX - A VBX FOR STORING AND RETRIEVING RESOURCES IN VB PROGRAMS

This VBX is an attempt to make it easier for VB programmer to use resources 
like bitmaps, strings, icons, cursors and textfiles in their programs without 
having to deliver all these files separately with your program or store them
in a DLL or in a VB form.

The container VBX is nothing more than the name says: it's a container
of resources. Using the VBX involves the following steps:

1.   Start the RC-EDIT program. This program allows you to specify the
     bitmaps, cursors, icons, textfiles and strings that you'd like to 
     be compiled into the VBX. You select the type of  resource by 
     selecting it from the Edit-menu. The program is pretty self-
     explanatory.
     With RC-EDIT you can roam your harddisk(s) and select all the
     resources you'd like to use in your program. After you've specified
     the resources you want to use, type a name for the VBX (8 characters
     at most, 'LIBRARY' for example) and press the 'Start'-button. the
     RC-EDIT program will now perform the following steps:
     -   The CONTAINR.VBX will be copied to the name you've specified
         (LIBRARY.VBX for example)
     -   The CtlName of the VBX will be patched in the VBX and will
         become the name of the VBX with 'Rc' appended to it
         (LibraryRc for example)
     -   All the resources you've choosen will be compiled into
         the VBX.

2.   When the RC-EDIT program is done, you should have a new VBX that
     has all the resources in it. You can add this VBX to your Visual 
     Basic project and add an instance of it to a form in your project.

3.   Now it's time to retrieve the resources from the VBX. They're stored
     in property array's. That means that they're not available at design
     time, but that's allright. You only need them at run-time.
     The following property arrays are present:

	Picture		Visual Basic Picture property array.
                        For example: Image1.Picture = LibraryRc1.Picture(1)
	hBitmap		Windows bitmap handle. This is the same
                        picture as in the Picture property array, but you
                        can only use it with API-calls, e.g. BitBlt.
	hPalette	Windows palette handle. This is the palette from the
                        picture in the Picture property array. Also for use
                        with API-calls.
	hCursor		Windows cursor-handle. To use with the
                        SetCursor API-call for example.
	Icon		Visual Basic Icon property array.
			For example: Form1.Icon = LibraryRc1.Icon(1)
	hIcon		Windows icon-handle. The same icon, but only useful
                        for Windows API-calls.
	String          String Property array. You can use this to set 
			caption for example: Me.Caption = LibraryRc1.String(1)
	Text		Textfile Property array. Complete text-files for
                        displaying in TextBoxes (mind the 32Kb limit).

     The sample project in the SAMPLE directory, shows the use of all types
     of resources.

4.   The RC-EDIT program also creates a Visual Basic BAS-file that includes
     named constants for all the resources inside the VBX. To change the
     way the constants are built, select 'Include file' from the 'Options'
     menu, before pressing the 'Start' button.

5.   That's all there is to it.

A few remarks:

-  The hPicture, hPalette, hIcon and hCursor resources are only valid
   until you get another resource of the same type from the VBX. If you
   want to use more hPictures (or other h... resources) at the same time 
   in your program, you'll have to make a copy of the resource before trying 
   to attempt to get another resource of the same type from the VBX.
-  You can use as many Container VBX'es in your application as you like.
   Since the name of the control is changed by RC-EDIT for each new control
   you create with it, there is no conflict in windows library-names and
   visual-basic control-names.
-  The Container VBX and the RC-EDIT, RC and RCPP programs must be in the
   same directory. RC-EDIT does no error checking whatsoever, so make sure
   they're all there.
-  You use the VBX on your own risk. In no case shall SheAr software be
   liable for any damages that may result from using this VBX. If you use
   this VBX you agree to be bound by this notice.
-  If you like to give away copies of the VBX to friends, give them the
   full archive, including this notice.
-  The container VBX is Shareware. You may use the VBX for 21 days. If you
   like it and want to continue using it, you'll have to register it.
   Registration fee is 20 US dollars and it will give you the following:
   - the latest version of the VBX.
   - a printed manual.
   - online-help (in the VBX and in the RC-EDIT program).
   - additional support for Metafiles and Version information in the VBX.
   - examples of using more than one h... resource at the same time
     (see first remark).
   - free updates for a full year.
   - free support (telephone or e-mail).
   To order, mail in the order form (ORDER.FRM) in this package.

If you have any questions about this VBX or if there's anything else you'd
like to know, don't hesitate to contact us through e-mail:

vbx_dev@shear.iaf.nl

Arjen Broeze
SheAr software
