Message-Id: <199711011350.IAA29237@delorie.com>
From: Brett Leslie Porter <blp01 AT uow DOT edu DOT au>
Subject: ANNOUNCE: ScreenFX for Allegro
To: djgpp-announce AT delorie DOT com
Date: Sat, 1 Nov 1997 15:53:20 +1100 (EST)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk
Precedence: bulk

ScreenFX Version 1.0
Released 1st Nov 1997

Hi there DJGPP (and Allegro) users!

Well, here's my first attempt at using Allegro, and I've gotta say, it makes
it a lot easier! Especially when writing routines like these screen effects.

ScreenFX is a set of routines to provide transitions or effects of whole
screens or just sprites (see example program for a demonstration)

There are two zip files, downloadable from:
   http://www.geocities.com/SiliconValley/Park/7483/
            ... in the DJGPP section

The routines support any resolution (in Allegro 2.2) and any sized bitmap.
The zero index colour is always a mask presently.

Included in the package is screenfx.h screenfx.o, and there is a seperate
test package with testprog.c, frame1.pcx, frame2.pcx and frame3.pcx. The
simplest way to compile the testprog is to type:
   gcc -O3 -m486 -o testprog.exe testprog.c screenfx.o -lallegro

The source, screenfx.c is available to everyone, but you must contact me to
get it, so that I can keep track of it. 

There are currently 17 transitions included. To use just #include screenfx.h
and use pInitialise(card, xdim, ydim) to set it up. This will call
allegro_init, pRandomize and set_gfx_mode for you. If you don't want to use
pInitialise, make sure you call pRandomize so that the bleed routine isn't
always the same. You can also use the pRandom function in your own routines.

Conditions:
   It's free and you can do what you want, but it is copyrighted, so you can't
   just rip it off. Basically same rule as Allegro. I'd appreciate some
   credit :) If you want to modify it (by obtaining the source), you should
   tell me what you intend to change/add. I may already be working on it or
   may want to include it, so just run it past me first.

Sorry about the lack of documentation and the lack of optimization, I've
been busy. Feel free to help me improve it!

Also note that this will be included as part of the upcoming release of
XTools v1.7, from FuzzySoft. Thanks to Chris for getting me going on this in
the first place.

Wish list:
   * Make 'em faster!
   * Support Allegro WIP (well, actually, I'm waiting for v3.0)
   * Add more routines

Send all correspondence to blp01 AT uow DOT edu DOT au.

Hope you like them!

-- Oh yeah, That groovy logo of mine is copyright too, 1992. Don't pinch it
(not that you'd want to! :)

Brett