Xref: utzoo comp.sys.ibm.pc:40924 comp.sys.mac:45247 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!apple!rutgers!netnews.upenn.edu!eniac.seas.upenn.edu!hodas From: hodas@eniac.seas.upenn.edu (Josh Hodas) Newsgroups: comp.sys.ibm.pc,comp.sys.mac Subject: Re: Multiple monitors (was: Xerox sues Apple!) Message-ID: <18570@netnews.upenn.edu> Date: 30 Dec 89 16:54:34 GMT References: <2938@infmx.UUCP> Sender: news@netnews.upenn.edu Reply-To: hodas@eniac.seas.upenn.edu.UUCP (Josh Hodas) Distribution: usa Organization: University of Pennsylvania Lines: 75 In article <2938@infmx.UUCP> aland@infmx.UUCP (alan denney) writes: >dorourke@polyslo.CalPoly.EDU (David M. O'Rourke) writes: >>[and I've tried so hard to stay out of this... :-) ] >> >> You've obviously not ever used a system that allowed you to use two screens >>effectivly. It's very nice to debug on one screen and run your code on the >>other, just as much as simply having the extra screen real-estate. >>... >> You could've very easily picked some of the expanssion options that are >>truely debatable for usefullness, but saying the ability to configure a >>multi-screen system is not a USEFUL system just shows how closed minded and >>un-imformed you really are. > >Uh, Dave, how much have you used PCs? As stated earlier, I have been running >two monitors in my AT at home for quite a while, and I use them both for >dual-screen debugging also. What makes you think the PC world is incapable >of such magic? > >Tough to configure, too. Open the machine, add the mono card, screw it in, >close the machine, turn on the power. No switches to set, no muss, no fuss. >To switch primary monitor to the mono, run "mode mono". To switch back to >EGA, run "mode co80". To enable the secondary monitor in the Informix-4GL >debugger (for example), run "appl dev" (application device enable). >Gee, that didn't hurt a bit. > >>David M. O'Rourke >>Graduating in March of 1990, with a BS in Computer Science & need a Job. > >In a Mac-only shop, I suppose... > >-- > Alan S. Denney @ Informix Software, Inc. "We're homeward bound > {pyramid|uunet}!infmx!aland ('tis a damn fine sound!) > -------------------------------------------- with a good ship, taut & free > Disclaimer: These opinions are mine alone. We don't give a damn, > If I am caught or killed, the secretary when we drink our rum > will disavow any knowledge of my actions. with the girls of old Maui." God forgive me.. I swore I was going to stay out of this argument. I thought I had resisted it long enough, as the volume was down to a trickle. But this note just P-sses me off. (It's not the first one, its just the straw that broke the camel's back. Alan, you clearly have no idea what this conversation is about. Yes, it is certainly true you can run your debugger on two screens. I wont deny that, I do it all the time when I do PC development. But the point is that this debugger had to be specifically designed for that use, and it is one of a very few applications that knows how to do it on the PC. On the mac any application can run on anny monitor (caveat, a very few poorly written programs may map their window to a particular location, this is a serious flaw in those programs). This helps, not just with individual programs that use lots of windows, (for instance when I am TeXing I keep my preview window open on my Portrait display while I type on my 13" color screen) but also when using several programs together. I might bring up MacWrite II on the main screen (portrait) then bring up MacDraw to do a diagram. It opens onto the main screen, but I just drag it over to the small screen, so I can see both programs at once. Again the poin is not that a very few programs on the PC can use this capability. THe point is that you have no idea how useful a general feature it is until you have used a well designed system that lets you use it at will. Josh ------------------------- Josh Hodas (hodas@eniac.seas.upenn.edu) 4223 Pine Street Philadelphia, PA 19104 (215) 222-7112 (home) (215) 898-5423 (school office)