home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!psuvax1!rutgers!cbmvax!andy
- From: andy@cbmvax.commodore.com (Andy Finkel)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Newbie font/screen question
- Message-ID: <38110@cbmvax.commodore.com>
- Date: 22 Dec 92 15:01:43 GMT
- References: <37971@cbmvax.commodore.com> <paulk.2vmr@terapin.com>
- Reply-To: andy@cbmvax.commodore.com (Andy Finkel)
- Organization: Flying Cat, Inc.
- Lines: 39
-
- In article <paulk.2vmr@terapin.com> paulk@terapin.com (Paul Kienitz) writes:
- >> Indeed, the correct way is:
- >>
- >> if ( OpenDiskFont( ... ) )
- >> {
- >> if ( OpenScreen( ... ) )
- >> {
- >> ...
- >> CloseScreen( ... );
- >> }
- >> CloseFont( ... );
- >> }
- >
- >At some time in the past I found that calling OpenDiskFont() will
- >always load from disk even if the font is already in memory. So I
- >call OpenDiskFont() only if OpenFont() fails. Is this still
- >necessary with the latest versions?
-
- When you call OpenDiskFont, it looks at the fonts currently loaded
- into ram, to decide if any of them is a close enough match to what
- you are asking for to be used. Before 2.0, OpenDiskFont was picky
- about what constituted a match. Very picky. Unbelievably picky.
- So picky, in fact, that it would almost never decide that what you had
- in ram was acceptable. Under 2.0, a more rational scheme
- was adopted that will result in the ram copy of font you've previously
- OpenDiskFonted being found in ram by a subsequent OpenDiskFont.
-
- Occasionally you may still want to do an OpenFont first; this allows
- you to use your own judgement about what constitutes an acceptable
- match. For many purposes, however, this is now unnecessary.
-
- andy
- --
- andy finkel andy@cbmvax.commodore.com
-
- "Unix is the Operating System of the future, and always will be."
-
- Any expressed opinions are mine; but feel free to share.
- I disclaim all responsibilities, all shapes, all sizes, all colors.
-