Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!cbmvax!bj From: bj@cbmvax.commodore.com (Brian Jackson) Newsgroups: comp.sys.amiga.tech Subject: Re: Opening a diskfont?? Message-ID: <17280@cbmvax.commodore.com> Date: 9 Jan 91 17:01:57 GMT References: <700@cbmger.UUCP> <1991Jan8.173617.12144@msuinfo.cl.msu.edu> <706@cbmger.UUCP> Reply-To: bj@cbmvax.commodore.com (Brian Jackson) Organization: Commodore, West Chester, PA Lines: 31 In article <706@cbmger.UUCP> peterk@cbmger.UUCP (Peter Kittel GERMANY) writes: >Question to those with wisdom: >Could it be that OpenDiskFont() is intelligent enough to look into >RAM first, without explicitly calling OpenFont()? Or that a >duplicate font gets loaded over an already existing one in RAM? From the 1.3/2.0 autodocs: NAME OpenDiskFont - load and get a pointer to a disk font. FUNCTION This function finds the font with the specified textAttr on disk, loads it into memory, and returns a pointer to the font that can be used in subsequent SetFont and CloseFont calls. It is important to match this call with a corresponding CloseFont call for effective management of font memory. >>>> If the font is already in memory, the copy in memory is used. <<<< >>>> The disk copy is not reloaded. <<<< bj >Best regards, Dr. Peter Kittel ----------------------------------------------------------------------- | Brian Jackson Software Engineer, Commodore-Amiga Inc. GEnie: B.J. | | bj@cbmvax.cbm.commodore.com or ...{uunet|rutgers}!cbmvax!bj | | "My beer comes from farther away than your beer." | -----------------------------------------------------------------------