Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mcnc!uvaarpa!murdoch!astsun.astro.Virginia.EDU!gl8f From: gl8f@astsun.astro.Virginia.EDU (Greg Lindahl) Newsgroups: comp.sys.atari.st Subject: Re: Resource Conversion Keywords: RCS,Mono,Colour Message-ID: <1990Dec16.021921.8063@murdoch.acc.Virginia.EDU> Date: 16 Dec 90 02:19:21 GMT References: <70342@bu.edu.bu.edu> <110968@convex.convex.com> Sender: news@murdoch.acc.Virginia.EDU Distribution: usa Organization: Department of Astronomy, University of Virginia Lines: 20 In article <110968@convex.convex.com> rosenkra@convex.com (William Rosencranz) writes: > >the long answer is to look at rsrc_obfix AES call. this converts from >character coords (what res construction set puts out) to pixel coords. >i believe this takes resolution into account. i also believe this may >be done by rsrc_load automatically. A long time ago, I looked into this for TeXShell, so I could spell it with an 'E' half a line down. I had used rsctoc to imbed the resource into my C program. Upon looking at the stuff in the resource file, it was obvious that all coordinates were stored as 256*pixels + characters. And the fixup-routine just knew how many pixels tall and wide a character are, and converted everything to pixels. So all you have to do is modify the fixup routine to treat the pixel offsets in a resolution-independent fashion, and you're all set. >this is for memory, and i have not written AES/VDI code in quite some time. Ditto.