Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!caen!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.041619.29085@kuhub.cc.ukans.edu>
Date: 16 Mar 91 10:16:19 GMT
References: <12364@pt.cs.cmu.edu>
Organization: University of Kansas Academic Computing Services
Lines: 18

In article <12364@pt.cs.cmu.edu>, hairston@henry.ECE.CMU.EDU (David Hairston) writes:
> 
> how do you determine when it is absolutely safe to use NewCWindow
> as opposed to NewWindow?  i'm confused by the all things you can
> test and their implications (i.e. sys environs and gdFlags, etc.).
> i'd like to use NewCWindow unless the hardware absolutely prohibits
> this, in which case my newWindow() function would use NewWindow
> instead.
> 
>   -dave-  
> hairston@henry.ece.cmu.edu

I'm pretty new to color, but I believe you need to call SysEnvirons first for
HasColorQD.  If the machine HasColorQD then you can call NewCWindow.  The only
reason to check gdFlags would be to determine the bit-depth (I think).  But,
even if they're running a bit depth of 1, if they have color QD...it don't
matter.
john calhoun