Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!decvax!decwrl!labrea!Shasta!mrh
From: mrh@Shasta.STANFORD.EDU (Marc Hannah)
Newsgroups: comp.sys.mac
Subject: Re: Compatibility guidelines
Message-ID: <1583@Shasta.STANFORD.EDU>
Date: Thu, 7-May-87 13:33:52 EDT
Article-I.D.: Shasta.1583
Posted: Thu May  7 13:33:52 1987
Date-Received: Sat, 9-May-87 09:49:07 EDT
References: <2227@crcge1.UUCP>
Organization: Stanford University
Lines: 16
Keywords: Machine-independent coding
Summary: no tabs in TextEdit yet, screen question included

In article <2227@crcge1.UUCP>, ranson@crcge1.UUCP writes:
>  Another (unrelated) question: Does the new TextEdit support tabs?
>      Daniel Ranson

    Unfortunately TextEdit doesn't support tabs in the new release. Too bad.
     
   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?

David Gelphman   daveg%slacvm.bitnet@forsythe.stanford.edu