Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!rosie!aozer From: aozer@next.com (Ali Ozer) Newsgroups: comp.sys.next Subject: Re: bits per pixel (was: NeXT General Educational Disqucount?) Message-ID: <728@rosie.NeXT.COM> Date: 15 May 91 01:46:08 GMT References: <1991May12.052853.27513@neon.Stanford.EDU> <2776@public.BTR.COM> Sender: news@NeXT.COM Distribution: usa Organization: Next Computer, Inc. Lines: 20 Nntp-Posting-Host: twinpeaks.next.com In article Scott Hess writes: > ... Also, the window won't get deeper (in bits) than the hardware supports. It can; however, by default, apps limit the window depth limits to the depth of the deepest frame buffer available to the system. You can increase (or decrease) this depth limit through the setDepthLimit: method in Window or setwindowdepthlimit operator in the window server. NXImage also provides a method to allow you to open image files in their full depth (rather than the depth limit of the app). > ... 8-bit deep monochrome. I'm not sure what the alpha on this depth is, but >it's probably 4 or 8 (2 would seem a little limiting). Eight; depth of the alpha channel is the same as the depth of the other channels (grayscale channel or each channel of RGB). This fits nicely into the PostScript model of image data. Ali, Ali_Ozer@NeXT.com