Xref: utzoo comp.sys.mac:34583 comp.sys.mac.programmer:7482
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!intercon!amanda@intercon.uu.net
From: amanda@intercon.uu.net (Amanda Walker)
Newsgroups: comp.sys.mac,comp.sys.mac.programmer
Subject: Re: Quickdraw efficiency question
Message-ID: <1167@intercon.UUCP>
Date: 11 Jul 89 17:35:51 GMT
References: <1681@neoucom.UUCP>
Sender: news@intercon.UUCP
Reply-To: amanda@intercon.uu.net (Amanda Walker)
Organization: InterCon Systems Corporation
Lines: 21

In article <1681@neoucom.UUCP>, sam@neoucom.UUCP (Scott A. Mason) writes:
> Intuitively, I would think that DrawString would be faster, but then again,
> doesn't DrawString make repeated calls to DrawChar?  BTW, I want to do this
> for a terminal emulation program, and want maximum screen drawing speed.
> 
> While I'm at it, how does Mackermit achieve such speedy screen drawing??

Building a string and drawing it with DrawString (or DrawText) is *much*
faster.  This is what MacKermit does.  This is one case where your initial
intuition about which would be faster is wrong.  As it turns out, DrawChar
is done by drawing a string of 1 character...

One of the reasons for the speedup is that the font information is retrieved
once per string, so the fewer times this is done, the faster the text shows
up.

--
Amanda Walker
InterCon Systems Corporation
--
amanda@intercon.uu.net  |  ...!uunet!intercon!amanda