Path: utzoo!utgpu!attcan!uunet!husc6!mailrus!utah-gr!utah-cs!sunset.utah.edu!u-jmolse From: u-jmolse%sunset.utah.edu@utah-cs.UUCP (John M. Olsen) Newsgroups: comp.sys.amiga.tech Subject: Re: Message from designer of FlickerFixer Message-ID: <5668@utah-cs.UUCP> Date: 21 Aug 88 17:14:18 GMT References: <3348@crash.cts.com> Sender: news@utah-cs.UUCP Reply-To: u-jmolse%sunset.utah.edu.UUCP@utah-cs.UUCP (John M. Olsen) Organization: University of Utah, Computer Science Dept. Lines: 46 In article <3348@crash.cts.com> haitex@pnet01.cts.com (Wade Bickel) writes:This would be fixable *if* the Amiga matched the short and long frames <>instead of ignoring them for *update* purposes. Things move between each <>frame, whether long or short. The above example would be great if Ami <>didn't change things between (for example) short[0] and long[1] as well as <>between long[1] and short[2]. Several things are updated in screen memory < < However, when you write into say, a 320x400 bitmap, that is exactly