Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!bloom-beacon!think!ames!ucbcad!ucbvax!hoser.berkeley.edu!bryce From: bryce@hoser.berkeley.edu (Bryce Nesbitt) Newsgroups: comp.sys.amiga Subject: Re: Badge Killer Demo Contest disks Message-ID: <21786@ucbvax.BERKELEY.EDU> Date: Sat, 14-Nov-87 05:01:48 EST Article-I.D.: ucbvax.21786 Posted: Sat Nov 14 05:01:48 1987 Date-Received: Sun, 15-Nov-87 16:59:24 EST References: <21732@ucbvax.BERKELEY.EDU> <1869@cadovax.UUCP> Sender: usenet@ucbvax.BERKELEY.EDU Organization: University of California at Berkeley Lines: 47 In article <1869@cadovax.UUCP> keithd@cadovax.UUCP (Keith Doyle) writes: >In article <21732@> bryce@hoser.berkeley.edu (Bryce Nesbitt) writes: > >> k> Does it work with interlaced and/or oversized Workbenches? -8 if >> not. An additional -2 if the demo has a window that is arbitrarily >> restricted to 640*200 pixels. > >What's the definition of "arbitrarily" here? Arbitrary means that, the application supports a larger window size than the Window's "maximums" are set to. Case in point: (Some of the) Infocom games support word-wrapping to your current window size, make the window smaller and it adjusts. The maximums are set to 640*200. This is 255% smaller than my 704*464 display allows. Merely by filezaping the constants in the program code I can modify the progam to use the space... it works. Remember programmers... set the window maximums to whatever the maxium *your* application can support, even if it is larger than the current screen you own. To specify "no limits", set the size fields to ~0 (or -1, same thing). The Intuition manual example is *wrong* in encouraging 640*200. >I have a comment about this. I don't think it should be required that >the demo should run once and then quit... Yes, I agree. An advanced user could set up a script, naturally. Infinite loops are desirable for dealer demos. A slideshow of all the demos on the disk would be even better, but then each demo would need to automatically exit. >Dealers like to see demos that >loop forever so they can leave them running on the machine. RGB was >set up to run once and then quit (because it was in the contest rules) >but now we are trying to get everyone a version that loops because that's >what the stores want. Having two versions out there is a pain. I suggest using "LOOP=ON/OFF" in the tooltypes. *One* version would serve both. Also it needs to be easily abortable, the invisible gadget in the upper left seems to be a workable de-faco standard. |\ /| . Ack! (NAK, SOH, EOT) {o O} . bryce@hoser.berkeley.EDU -or- ucbvax!hoser!bryce (") U