Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!brutus.cs.uiuc.edu!uakari.primate.wisc.edu!uflorida!mephisto!udel!rochester!kodak!elmgate!jeh
From: jeh@elmgate.UUCP (Ed Hanway)
Newsgroups: comp.sys.amiga.tech
Subject: Re: How do you draw to the screen quickly? (The real solution)
Message-ID: <1204@elmgate.UUCP>
Date: 15 Feb 90 17:49:43 GMT
References: <1092@mindlink.UUCP> <9231@cbnewsm.ATT.COM>
Sender: jeh@elmgate.UUCP
Reply-To: jeh@elmgate.UUCP (Ed Hanway)
Distribution: na
Organization: Eastman Kodak Company, Rochester, NY
Lines: 19

In article <9231@cbnewsm.ATT.COM> nsw@cbnewsm.ATT.COM (Neil Weinstock) writes:
>Geez, you guys are all missing the obvious and correct solution.  The
>answer, as it almost always is, is to use a lookup table.  Use the data for 
>each scan line as the lookup index (simply concatenate the pixel values into
>one long binary value), and put the corresponding Image structure into that 
>table entry.  So, you just take the data, look up the appropriate scan line, 
>and use DrawImage().  Only one operation per scan line.  How much quicker
>can you get?

It's a joke, right? My calculator gave up but "bc" dutifully told me
that a look-up table for each possible low-res scan line would take
3176248838703735071388317970997340557438739699483247316076389267090944\
8424296143487586179936927258864875554241803836083347728168482432449060\
4855548268961204923221725750403452934972636403246568312773419816518854\
1019193627059188378560474396174450152676920272486972400155193608576973\
9549574787063085604610601339929877328920047078547471584268060390863192\
35148982818821631076219391836160 megabytes of RAM, assuming 4 bit planes.

So are you going to post the table? :-)