Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!willett!ForthNet From: ForthNet@willett.UUCP (ForthNet articles from GEnie) Newsgroups: comp.lang.forth Subject: Graphics Message-ID: <610.UUL1.3#5129@willett.UUCP> Date: 3 Mar 90 05:15:21 GMT Organization: Latest link in the ForthNet chain. (Pgh, PA) Lines: 55 Date: 03-02-90 (01:47) Number: 1769 (Echo) To: MIKE SPERL Refer#: 1754 From: MARK SMILEY Read: NO Subj: DGIF1.ZIP Status: PUBLIC MESSAGE Mike, Glad to see you're back. Your system sounds excellent, and at an unbelievably low price, too! I am currently seeking a job, but once I get settled in, I'll consider upgrading my system. I had trouble with SHOWGIFINFO on two .GIF files that are viewable with other gif viewers. One was a 320x200 256-color file, and the other was a 640x480 256-color file. In both cases, SHOWGIFINFO gave the message: Not a gif file. If it would help you, I could send you one of these gif files. SHOWGIFINFO did work on a 640x350 16-color .GIF file, though. By the way, pay no attention to the actual structure of the header in BRECALL -- that was for a particular program I wrote. I'm sending a new copy of the graphics routines to ECFB soon. It includes your EGA/VGA screen saving routines. > New-expect even workss with Tom's editor now without forcing you to do > a warm boot to get bacck to forth. Is this a new version of New-expect? I'd like to use it, but I gave it up due to incompatibilities with F-PC v. 3.50. > ... but miss the editor's help screens > that accompanied previous veersions (I don'tt use it enough to be > fully conversant with aall the keystrokes). Neither do I. I use QEDIT v. 2.08. > Hope I didn't cause you any trouble suggesting a change in DEFER. No trouble. I wisely (it seems with hindsight) decided to wait a bit before fooling with it. > DEFER ... > Maybe someone more familiar with the metacompiler would be interested > to help? Perhaps Tim Smith might be able to help, since he was re-writing the meta-compiler last I heard. > Meanwhile, I thought consideration might be given to a more efficient > jump table mechanism to direct a program to the correct code, > eliminating the use of defer if possible. What do you think? Sounds good to me. Any speed is helpful with graphics routines, and we are currently using tons of deferred words for nearly everything (dots, lines, etc.). So it could be quite an improvement. Mark --- ~ EZ-Reader 1.13 ~ ----- This message came from GEnie via willett through a semi-automated process. Report problems to: 'uunet!willett!dwp' or 'willett!dwp@gateway.sei.cmu.edu'