GIF, hell yeah!

KAY> Salute JTN!
wah, hello, long time no see;-)

KAY> 04/19/02 at 18:03:12 you wrote:
VK>> gigascreen in real life. In fact, this gigaskrin is not needed at all,
VK>> IMHO. There is no sense in it (some may say that it
VK>> increases the vertical resolution by 2 times - this is nonsense). If
VK>> you have a Pentagon, it’s better to download Stellar Contour, - the demo from
VK>> last year’s CC, - there the gigascreen is implemented in software.

KAY> The software GIGASCREEN needs to be fixed for a specific time frame (N cycles
KAY> per line), and with high accuracy: switching screens should
KAY> occur during drawing border, otherwise it will be ugly.
KAY> Two commands for each line - at least: XOR #08 ;7 bars
KAY> OUT (#FD),A ;11 bars
KAY> 18 bars * 192 lines = 3456 bars. The restrictions imposed on the
KAY> program executed in the remaining time are obvious: the program must
KAY> be broken into pieces of length 224-18=206 cycles (for Pentagon).

KAY> Hardware G$ is a universal solution. OUT (0xEFF7),0x10 - and there are no
KAY> problems ;)
the point is that there is no expediency in the gigascreen itself. I speak as a coder, it makes no sense to do effects under the iron g$, and it makes no sense to show graphics either. So
I'll look again at SC andI’ll think: “Yes... damn, well, Vivid got screwed there
with the fix, we don’t need such “happiness”” ;-).
By the way, I already figured out how to break almost any program (meaning demo) into pieces of xx
cycles a long time ago, and I wrote about it here a few months ago;).

JTN/4D