mrh@Shasta.STANFORD.EDU (Marc Hannah) (09/09/87)
I have run into problems trying to use the two new Color QuickDraw (WM)
calls GetNewCWindow and CopyPix. I recall recently reading that these
calls have been eliminated or renamed. This is believable since the
linker cannot resolve references to these calls. I seem to recall that
the CopyPix call has been eliminated and is replaced by a plain old
CopyBits call with pixmaps instead of bitmaps. Is this true?
I am at a loss to figure out where the GetNewCWindow call went to.
Any help there?
Thanks all,
David Gelphman daveg%slacvm.bitnet@forsythe.stanford.eduneil@beowulf.ucsd.edu (Neil Rhodes) (09/10/87)
In article <2001@Shasta.STANFORD.EDU> mrh@Shasta.STANFORD.EDU (Marc Hannah) writes: > > I have run into problems trying to use the two new Color QuickDraw (WM) > calls GetNewCWindow and CopyPix. I recall recently reading that these > calls have been eliminated or renamed. This is believable since the > linker cannot resolve references to these calls. I seem to recall that > the CopyPix call has been eliminated and is replaced by a plain old > CopyBits call with pixmaps instead of bitmaps. Is this true? > I am at a loss to figure out where the GetNewCWindow call went to. > Any help there? > > Thanks all, >David Gelphman daveg%slacvm.bitnet@forsythe.stanford.edu My APDA draft of IM V has no mention of CopyPix, though it does mention CopyPixMap, which is alive and well in both the C and Pascal include files in MPW 2.0. CopyBits can handle PixMaps as well as BitMaps, so CopyPixMap seems superfluous (I have never used CopyPixMap, but always use CopyBits for copying PixMaps). GetNewCWindow is also present. Traps for these two calls are: CopyPixMap aa05 GetNewCWindow aa46 Neil Rhodes Palomar Software, Inc. c/o UC San Diego neil@sdcsvax.ucsd.edu
stew@endor.harvard.edu (Stew Rubenstein) (09/10/87)
In article <2001@Shasta.STANFORD.EDU> daveg%slacvm.bitnet@forsythe.stanford.edu (David Gelphman) writes: > > I have run into problems trying to use the two new Color QuickDraw (WM) > calls GetNewCWindow and CopyPix. I recall recently reading that these > calls have been eliminated or renamed. They have indeed been eliminated. CopyBits will now handle a PixMap as well as a BitMap, and GetNewWindow creates a color window if there is a 'wctb' resource with the same ID as the WIND resource. Stew Rubenstein Cambridge Scientific Computing, Inc. UUCPnet: seismo!harvard!rubenstein CompuServe: 76525,421 Internet: rubenstein@harvard.harvard.edu MCIMail: CSC
mrh@Shasta.STANFORD.EDU (Marc Hannah) (09/10/87)
In article <2816@husc6.UUCP>, stew@endor.harvard.edu (Stew Rubenstein) writes: > In article <2001@Shasta.STANFORD.EDU> daveg%slacvm.bitnet@forsythe.stanford.edu (David Gelphman) writes: > > They have indeed been eliminated. CopyBits will now handle a PixMap > as well as a BitMap, and GetNewWindow creates a color window if there > is a 'wctb' resource with the same ID as the WIND resource. > > Stew Rubenstein Will the REAL Inside Mac Volume V please stand up. Golly it is tough sometimes. The CopyBits <-> CopyPix change I could believe and figured it out. The use of GetNewWindow makes sense so you can color a window without making changes to the source code. What really threw me off however is: 1. The LSC, LSP, and the MPW Assembler interfaces all have a GetNewCWindow call or trap. 2. Compiling the code with GetNewWindow and Fediting the GetNewWindow opcode to GetNewCWindow worked fine. From this I gather that the already existing Rom code will not be supported on direct call. Thanks to those who replied on this. David Gelphman daveg%slacvm.bitnet@forsythe.stanford.edu