Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!seismo!sundc!pitstop!sun!amdcad!ames!mailrus!tut.cis.ohio-state.edu!rutgers!bellcore!jcricket!sjs
From: sjs@jcricket.ctt.bellcore.com (Stan Switzer)
Newsgroups: comp.windows.news
Subject: Re: Canvases in negative space
Keywords: Transformations
Message-ID: <11313@bellcore.bellcore.com>
Date: 26 Oct 88 15:19:53 GMT
Article-I.D.: bellcore.11313
References: <646@ecrcvax.UUCP> <21066@sgi.SGI.COM>
Sender: news@bellcore.bellcore.com
Reply-To: sjs@jcricket.UUCP (Stan Switzer)
Organization: Computer Technology Transfer, Bellcore
Lines: 27

In article <21066@sgi.SGI.COM> msc@canth.SGI.COM (Mark Callow) writes:
> 2.	The second problem is that the underlying pixrect code does
> 	not understand how to make region pixrects that are to top
> 	or left of the primary pixrect.  The underlying code called
> 	by movecanvas as tests to prevent -ve x or y values.  It
> 	sets them to zero.

I'm glad you guys fixed this problem, and I hope Sun does the same.
Some things would be quite a bit simpler without this restriction.

But ...

As with any other "feature," nice or not, changing its behavior will
lead to some interesting effects.  An funny one comes to mind:

Closing a window for the first time places the icon at the upper left
corner of the window.  If the window were placed such that the upper
left corner were off-screen (currently an impossibility) then the icon
would materialize off-screen and there would be no way to open the
window again!

Myself, I have already hacked a window subclass (based on Don Hopkins
neatwin.ps) that initially places the window at the mouse cursor.  In
addition, pushing the "close button" with "Middle" causes an "iconize
and slide icon" behavior.

Stan Switzer  sjs@ctt.bellcore.com