🚀 go-pugleaf

The president of our users group is the author of the best (IMHO) IFF viewer
available!  He is currently working on the upgrade to 3.0 (tentatively called
3.1) but just received a decidedly nasty blow:

Supeview has a routine (which he authored of course) which will read in the
appropriate BMHD, color tables etc. (I'm no IFF guru, just the relay man) and
then reads in and decodes the picture to memory.  The it returns where the
screen is opened.  This technique is necessary to handle SHAM and superbitmap
pictures.  Unfortunately, as David found out this week by trying out his program
on a 2.02 developer's machine (I know, that violates the non-disclosure thingy,
but heaven forbid we support PD authors who make little if any money on their
work as much as the commercial software companies.  What's a little test to
save the PD author the deluge of mail when his program crashes under the new
OS that he hasn't even seen - editorial comment), this method fails miserably.
In 1.3, intuition erased the area under the title bar.  He fixed this by
blitting this area until after the screen was opened (behind of course) and
then replacing the area.  Well as of 2.02, the whole screen is cleared when
a newscreen is opened.  Now SuperView doesn't work AT ALL!  Well, as David
said "They are clearing the bitmap that I pass them, I just hope they left me
a flag that I can set to stop that."  WELL?  Any 2.0 gurus out there know how
he can get around this?  By having to open up the screen before decoding the
picture, superbitmaps and SHAMs require him to close the screen and re-open
it when it is discovered that they are such things.  Since these chunks aren't
always near the beginning, this is very inefficient and would slow things
considerably.  Any help would be greatly appreciated and will be passed on
verbatim to David.  Thanx.

Rick Tillery