Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!spool2.mu.edu!samsung!cs.utexas.edu!asuvax!stjhmc!p88.f15.n300.z1.fidonet.org!Lawson.English
From: Lawson.English@p88.f15.n300.z1.fidonet.org (Lawson English)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Mac II Disappointment/Request for Game Recs
Message-ID: <34584.278C73D5@stjhmc.fidonet.org>
Date: 8 Jan 91 18:58:58 GMT
Sender: ufgate@stjhmc.fidonet.org (newsout1.26)
Organization: FidoNet node 1:300/15.88 - Tucson Apple Core, Tucson AZ
Lines: 24

mlab2@kuhub.cc.ukans.edu writes in a message to All

M>  I can only speak for the games I've done, but enlarging the 
M> contents of the screen would be a major hassle. Alternate PICTs 
M> for the various monitor dimensions, a whole slew of variables 
M> where constants were, major if/thens all over the code. Perhaps 
M> it would even slow down the game to have all these extra branching 
M> thrown in. That may be okay with a word processor, but a game 
M> relies on all the optimization it can afford.

I'm currently designing an educational package that may run on different size
screens, may need to have resizable fonts for seeing-impaired students, etc.
There are no "if-then-else's" to decide how to big to make the screen: things
are merely scaled to the screen (with exceptions when it looks "funny"). I'm
using the TCL's with Think Pascal, so I have a resizable pane that takes its
location from the pane to the left and above, with a default to a fixed location
if there is no leftmost/abovemost pane.

Lawson
 

--  
Uucp: ...{gatech,ames,rutgers}!ncar!asuvax!stjhmc!300!15.88!Lawson.English
Internet: Lawson.English@p88.f15.n300.z1.fidonet.org