Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!maverick.ksu.ksu.edu!kuhub.cc.ukans.edu!2fmlcalls
From: 2fmlcalls@kuhub.cc.ukans.edu
Newsgroups: comp.sys.mac.programmer
Subject: Re: when to use NewCWindow?
Message-ID: <1991Mar16.225917.29112@kuhub.cc.ukans.edu>
Date: 17 Mar 91 04:59:17 GMT
References: <12364@pt.cs.cmu.edu> <1991Mar16.041619.29085@kuhub.cc.ukans.edu> <12376@pt.cs.cmu.edu>
Organization: University of Kansas Academic Computing Services
Lines: 22

In article <12376@pt.cs.cmu.edu>, hairston@henry.ECE.CMU.EDU (David Hairston) writes:
> assuming theWorld.hasColorQD why shouldn't i use NewCWindow() over
> NewWindow()?  i thought that was sufficient but i've read one glimmer
> of ambiguous info that leads me to believe that hasColorQD is required
> but not sufficient to insure use.  is this correct?  specifically, can
> a MacPlus or MacSE have color QD and not be able to support cGrafPorts?
> i don't think pixelSize is an issue here.
> 
> thanks for any and all info!
> 
>   -dave-  
> hairston@henry.ece.cmu.edu

Someone correct me if I'm wrong, but the Mac Plus and SE will not give you a
hasColorQD=TRUE.  The SE 30 I believe does have colorQD, but then also has the
ROM routines to support it (such as NewCWindow()).  So, I would guess that you
could call up a color window on an SE 30, but you would have displayed a black
and white window.

Anyone want to straighten us out?

john calhoun