home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Gold Fish 1
/
GoldFishApril1994_CD2.img
/
d4xx
/
d433
/
gwin
/
changes
< prev
next >
Wrap
Text File
|
1991-01-12
|
2KB
|
47 lines
This is a change history of GWIN
Release 1.0 - Initial Version
Release 1.1 - Maintenance Version
1. New Aztec Manx 5.0 compiler/linker is incompatible with earlier
versions of object code. Everything must be recompiled including
my GWIN object files gwin.ff.o, gwin.ffCD.o, and gwin.fiCD.o. You
need these new release 5.0 versions if you are using the 5.0 compiler
because the old object files will not link with object files created
using the new version of the compiler. Many thanks to Adam Benjamin
of Michigan for bringing this to my attention. I had not realized that
there was a problem until he called. I had been dragging my feet with
respect to getting the new compiler since I always try to avoid early
versions of software - Particularly compilers and operating systems.
So now I have version 5.0b. (Or is it c? My disks came with the "b"
scratched out and a "c" printed by hand.) I recompiled GWIN and that
is the primary reason for redistributing the software.
2. Due to a book-keeping error on my part, the LATTICE-related
object codes included on fish disk 322 (gwinl.ff.o, gwinl.ffCD.o,
and gwinl.fiCD.o) were not the versions I intended to include.
They represent a slightly earlier version. Glen Fullmer did a lot
of work creating the Lattice versions of the GWIN object files and
I blew it by not including the correct and most current version.
My apologies to Glen and to all you other Lattice users. The version
on 322 was functional unless you tried to use the global variables
in gwin.user.h. At least one of my examples used the globals.
The examples compiled and linked correctly for Glen back in Feb 89.
He checked them out again for me today. Everything works if you use
the versions on this disk. Thanks to Stephen L. Ferrell of Pittsburgh,
Pa. for bringing this problem to my attention.
3. Modified the uprint and uprnt1 text handling routines to handle
complement modes so that you can handle text like rubber-band lines
are handled. (Essentially sets the XOR mode within the INTUITEXT
structure if uset("comp") is in effect.)
4. Modified umove routine to handle the uset("ncli") operation more
logically. The rubberbandbox demo had a problem when the border was
included. The problem was that the umove routine was in effect applying
clipping when it should not have been. This has been corrected.