Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!bellcore!uunet!brunix!omh From: omh@cs.brown.edu (Owen M. Hartnett) Newsgroups: comp.sys.mac.programmer Subject: Re: when to use NewCWindow? Message-ID: <68864@brunix.UUCP> Date: 17 Mar 91 21:51:33 GMT References: <12364@pt.cs.cmu.edu> <68833@brunix.UUCP> Sender: news@brunix.UUCP Reply-To: omh@cs.brown.edu (Owen M. Hartnett) Organization: Brown University Department of Computer Science Lines: 25 In article francis@magrathea.zaphod.uchicago.edu (Francis Stracke) writes: >In article <68833@brunix.UUCP> omh@cs.brown.edu (Owen M. Hartnett) writes: > > I'm not saying that NewCWindow works like this, or that it doesn't work > >Good, because it doesn't. Think about it--it isn't even *present* >unless CQD is installed! > >Or do you think Apple foresaw what fields a CWindow would have and put >them into the original QuickDraw? Of course not. But many of the traps are patched to enable them to work retroactively with new features. Why should I have to test if colorQD is present and open a non-color window on old machines? Why not get a color window structure for both machines and eliminate the test? The only difference is that the color window has more fields. The additional fields shouldn't put that much of a burden on the memory of B/W machines. -Owen Owen Hartnett omh@cs.brown.edu.CSNET Brown University Computer Science omh@cs.brown.edu uunet!brunix!omh "Don't wait up for me tonight because I won't be home for a month."