Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!think!ames!dftsrv!mimsy!tove.umd.edu!folta
From: folta@tove.umd.edu (Wayne Folta)
Newsgroups: comp.sys.mac
Subject: Re: Re^2: Multiple monitors (was: Xerox sues
Message-ID: <21671@mimsy.umd.edu>
Date: 6 Jan 90 16:09:33 GMT
References: <2938@infmx.UUCP> <126900139@p.cs.uiuc.edu> <531@tci.bell-atl.com>
Sender: news@mimsy.umd.edu
Reply-To: folta@tove.umd.edu (Wayne Folta)
Distribution: usa
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 28

>
>>				I am just beginning to write code for
>>multiple monitors, and it seems to be the same old stupid story:
>
>>1.  Check if you have multiple monitors. 
>
>Why on earth would you care??

The Following is Speculation by a Beginning Mac Programmer:

I think I might know what's going on here.  In general, any application ever
written for a Mac (that followed IM guidelines) will work transparently on
multiple monitors--or so I assume.  HOWEVER, the keyword is "transparently".

Say, for example, you wanted to write a debugger that popped up on the second
monitor.  Then you wold obviously have to test for its existence and its
location as a part of the virtual desktop.  Another example would be, say,
an After Dark (a screen blanker) routine.  You might want each screen to 
have its own copy of the animation going at once, not one huge, screen-spanning
animation.

I believe that all applications start up in the designated "main" monitor, and
if you wanted things to come up on a second monitor, you have to do something
about it.  Is this correct?
--


Wayne Folta          (folta@cs.umd.edu  128.8.128.8)