Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!ncar!gatech!udel!princeton!phoenix!kadickey
From: kadickey@phoenix.Princeton.EDU (Kent Andrew Dickey)
Newsgroups: comp.sys.apple2
Subject: Re: Stellar 7 re-release
Message-ID: <5039@idunno.Princeton.EDU>
Date: 4 Jan 91 19:57:17 GMT
References: <10019@pasteur.Berkeley.EDU>
Sender: news@idunno.Princeton.EDU
Organization: Princeton University, Princeton, New Jersey
Lines: 25

In article <10019@pasteur.Berkeley.EDU> benji@euler.Berkeley.EDU writes:
>In article toddpw@nntp-server.caltech.edu (Todd P. Whitesel) writes:
>
>>also, 3200 pictures cannot use scan line interrupts on every line.there isn't
>>enough time once you count the interrupt manager overhead. you can use a few
>>(I believe dreamgraphix's 3200-sluggish edit mode does that) but not all of
>>them at once.
>
>Then why are 3200-color pictures called that?  If you can only have an
>interrupt every other line, say, then the most that can be managed is 1600
>colors.  Dreamgraphix is doing something besides just displaying the
>picture, so I can see the problem there, but an ordinary display program

Ummm, I don't know about the rest of you, but if I were to write a 3200
color viewer, I wouldn't use interrupts at all.  I'd poll the vertical
line register, and update the pallettes as necessary for each line.

Please, stop this silly thread.  Interrupts shouldn't be used for
everything.  (Besides, since most 3200 color picture viewers achieve the
pallette changes through stack tricks, interrupts must be DISABLED,
otherwise the interrupt would push stuff on the stack, which would
actually be the pallette area!).

Kent Dickey
kadickey@phoenix.Princeton.EDU