Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!purdue!decwrl!labrea!csli!wilson
From: wilson@csli.STANFORD.EDU (Nathan Wilson)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Centering Dialogs
Message-ID: <5533@csli.STANFORD.EDU>
Date: 20 Sep 88 17:56:18 GMT
References:  <10050018@eecs.nwu.edu>
Reply-To: wilson@csli.UUCP (Nathan Wilson)
Organization: Center for the Study of Language and Information, Stanford U.
Lines: 19

In article <10050018@eecs.nwu.edu> bob@eecs.nwu.edu (Bob Hablutzel) writes:
>>     There are several ways ['centering' a window on multlple screen
>> Mac] could be done: (1) Center over
>> ScreenBits.Bounds, which would probably put the dialog between screens.
>  To my mind, (1) is the best. This does _not_ center the dialog between 
>screens.
>BTW - this seems to be what most people are doing. Whether this is some
>grand scheme I am unaware of, or happy accident, I cannot say. I suspect
>happy accidents, however.

Actually there is at least a bit of a 'grand scheme' around this method.
screenBits.bounds is set to boundary of the window with the menu bar, but
some traps have been adjusted in IM-V so they will continue to 'do the 
right thing' even when passed this value.  E.g. MoveWindow, and DragGrayRgn
look to see if their limits are close to the values of screenBits.bounds
and if they are will substitute the appropriate values from GrayRgn's
bounding box.  This is definitely a hack but it seems like a reasonable
way to maintain the semantics of screenBits.bounds.
	Nathan Wilson