Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!oliveb!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga
Subject: Re: Resolution independent programming? - (nf)
Message-ID: <51586@sun.uucp>
Date: 2 May 88 19:08:14 GMT
References: <36900004@infovax.UUCP>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 20

In article <36900004@infovax.UUCP> tensi@infovax writes:
->I see some problems with the different resolutions coming up.  Most data 
->structures in Intuition are totally pixel oriented. This makes it complicated 
->to write programs for screens of different resolution.
->
->E.g. when setting up a requester professionally (do you like tiny fonts just 
->because you are using interlaced mode?) would require to find out screen
->resolution and the width and height (is there anything like IntuiTextHeight?) 
->of the current font (which should preferably be looking good on that screen).

Most information about fonts are available from the Font pointer in the 
Rastport you will be rendering into. Items of interest will be 
RP->TxHeight - Height of the font in pixels
RP->TxWidth  - Width of individual characters, don't use if the font is 
	       proportional.
RP->TxBaseline - The base line of the font. X,Y+Baseline will render a c
character in the screen with it's top at line Y.

--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.