home *** CD-ROM | disk | FTP | other *** search
- Path: nntp.teleport.com!sschaem
- From: sschaem@teleport.com (Stephan Schaem)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Fastest way to clear a Window?
- Date: 15 Feb 1996 19:12:52 GMT
- Organization: Teleport - Portland's Public Access (503) 220-1016
- Message-ID: <4g00jk$91e@maureen.teleport.com>
- References: <4fck5b$7mm@leofric.coventry.ac.uk> <oj691i5u7w2.fsf@hpsrk.fc.hp.com>
- NNTP-Posting-Host: kelly.teleport.com
- X-Newsreader: TIN [version 1.2 PL2]
-
- Steve Koren (koren@hpsrk.fc.hp.com) wrote:
-
- : sschaem@teleport.com (Stephan Schaem) wrote:
-
- : > : Use the gfx.library functions. They're there for a reason.
- : >
- : > Do not use the gfx function if you want speed on native chipset.
- : >
- : > Well, we dont agree... and beleive me you wont change my mind about this.
-
- : That's ok, you won't change mine either :-)
-
- : At the very *least*, though, consider using the gfx.lib functions if you
- : know that you aren't talking to the custom chipset. I don't really care
-
- Where do you get the idea I dont do just that?
-
- : what programs do when they're talking to the custom chips, because
- : custom chip resolutions are so poor these days that I never use them
-
- Its fine with me... I dont have a 17" monitor so 640(704) by 400(480)
- do the job nicely.
-
- : anyway. As long as programs behave themselves on gfx cards, that's all
- : that matters (to me anyway).
-
- You are not very picky, if behaviour is all that matter :)
-
- Stephan
-