This is a demo of the "T4 DIB Library", a new
method for loading images into any control
that supports either the VB "LoadPicture"
function, or can accept an "hDib" as image
input.

The following describes the full Shareware
version of the product.

This demo version is the same as Shareware,
but supports no more than 4 members per
library.

The Shareware version costs $79. FL residents
add 6.5% sales tax. Shipping is $7 for the
U.S., $12 outside. Included in the package
are two manuals - one for the library-building
utility, another for using the VBX in your
VB3 or VB4 program. Both have tutorials.

CompuServe members can register this Shareware
by GO SWREG, select #7733.

Product Highlights

T4DIBLIB is a Visual Basic add-on which
handles image management and processing in a
new way. It's ideal for such applications as
animation, galleries, multi-media "stills",
and any other application which uses "lots"
of image files.

This product consolidates individual image
files into a single quick- load library. Each
image is a "member" (1-32 character name),
and can be optionally compressed. The base
format used for storage is the DIB
(device-independent bitmap), but input image
files can be in any of a wide variety of
types.

The product's two primary components are the
T4DIBLIB.EXE utility, and the T4DILIB.VBX
custom control.

T4DIBLIB.EXE Utility

Using this utility, you can draw in a WIDE
variety of image files (list in a minute).
You can place the DIB images of these files
in a single library as "members". Each member
can have a name up to 32 characters, and can
optionally be compressed. For multi-image
files (e.g. some TIF's), you can choose which
images you want, and store each as a
different member.

Although the libraries can contain images as
high as 24 bpp (bits per pixel), it works
best with color depth of 1, 2, 4 and 8 bpp.

Each library you build can be a "public" or
"private" library. Private libraries are
read-only to your end-user. Public libraries
will be able to be managed by the next
enhancement, "dynamic library management".
This not-yet-ready VBX will allow the
end-user (through your program), to create
new public libraries, and add and delete
members. Private libraries can only be built
through T4DIBLIB.EXE.

Image types supported at this time: Most
variations of BMP, DIB, GIF, ICO, JPG, PCX,
RLE, TGA, TIF, and WMF.

T4DILIB.VBX Custom Control

This VBX is the interface between the DIB
library and the "target" control that's to
display the image. Through typical property
settings, you open and close libraries, and
select members for display in the target. The
target control can be one that usually gets
it image through VB's LoadPicture function,
or one that accepts an hDib directly. The VBX
can build either image-type. You just fetch
the image from the library into the VBX, then
assign the target control's Picture property
(or whatever its called) to the VBX's Picture
property, or hDib property to the VBX's hDib
property.

You can effectively keep images "resident" by
assigning one of these VBX's to each image.
You can even choose between keeping the
typically-smaller DIB resident, or if speed
is important, keeping the device-dependent
variation (PIC, in VB) resident. This makes
T4DIBLIB a valuable animation tool.

You can also, of course, get information
about the library and/or individual members
through the VBX's properties. Library
properties include filename, public or
private, and number of members. Member
properties include member name, member
number, color depth (bpp), size, what
compression is used.

Known Restrictions

As offered, this product does not support
Visual C++; however, developers with 16-bit
Visual C++ programs, and interested in this
product, should inquire about being a Beta
site. This version, may, in fact, work with
your program, and Beta testers receive gratis
copies.

This product performs best with 1,2,4,8-bit
images. Although it can be used for 24-bit
images, it may not compress them. Experience
has shown, however, the 8-bit renditions of
24-bit images are almost always adequate for
all but the most detailed work. I will note
that 24-bit images are not very desirable,
because of their extreme size and loading
time, and are generally used only if there is
no other workable choice.

Currently, all components are 16-bit, and, as
such, are essentially Windows 3.1 compatible.
It has been tested under Windows 95, however,
and no problems were encountered.

Marc Staley
6401 S. Westshore Blvd. #1120
Tampa FL 33611
(813) 837-0560
CIS 76513,1650