Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-lcc!pyramid!voder!apple!dgold
From: dgold@apple.UUCP (David Goldsmith)
Newsgroups: comp.sys.mac
Subject: Re: Compatibility guidelines
Message-ID: <732@apple.UUCP>
Date: Thu, 7-May-87 21:09:44 EDT
Article-I.D.: apple.732
Posted: Thu May  7 21:09:44 1987
Date-Received: Sat, 9-May-87 10:44:03 EDT
References: <2227@crcge1.UUCP> <1583@Shasta.STANFORD.EDU>
Reply-To: dgold@apple.UUCP (David Goldsmith)
Organization: Apple Computer Inc., Cupertino, USA
Lines: 24
Keywords: Machine-independent coding

In article <1583@Shasta.STANFORD.EDU> mrh@Shasta.STANFORD.EDU (Marc Hannah) writes:
>   I was wondering about another problem...The latest issue of MacTutor
>has an article by Dan Weston about handling the new screens. One thing
>I saw was that he passed the screenbits.bounds rectangle to his call to
>dragwindow. I assume that this effectively PREVENTS a window from being 
>dragged from screen to screen in a multiple screen environment. I believe
>that the screenbits.bounds rectangle corresponds to the size of the 
>'default' screen. Do the WindowManager calls handle this properly or will
>this kind of code cripple an application in a multiple screen environment?

The window manager on the Mac II uses a heuristic to decide whether you meant
"this specific rectangle" or "the screen" for your drag bounds.  I believe
that if the drag bounds are the same as those suggested in Inside Mac (inset
four pixels from the edges of the screen and the menu bar) it assumes you
meant "the desktop" and acts accordingly.
-- 
David Goldsmith
Apple Computer, Inc.
MacApp Group

AppleLink: GOLDSMITH1
UUCP:  {nsc,dual,sun,voder,ucbvax!mtxinu}!apple!dgold
CSNET: dgold@apple.CSNET, dgold%apple@CSNET-RELAY
BIX: dgoldsmith