Toward Release (was Re: [GEM-dev] new win32 build)

[james tittle]

hey chris,

On Mar 19, 2006, at 2:58 PM, chris clepper wrote:
> The bug so far only happens on dual g5, but if you have a dual g4  
> it might be interesting to test. It's still not clear what the  
> cause is, but multiple capture devices, especially if one is a DV  
> device, seem to be the trigger.  I haven't tested 10.3 and  
> Quicktime 6.5 either since neither of those are an option for me  
> anymore, but that info could be useful as well.  I will probably be  
> working with Apple on tracking down the issue soon, so hopefully  
> they can provide some (paid) help.

...I don't know if this has been solved, but while thinking and  
poking around regarding erich's more recent question about resource  
reclamation in film loading, I started looking into "setgworld()",  
which we don't use in film-handling (we do use SetMovieGWorld(), but  
is that enough by itself?), but we do use in pix_video (ie.  
SGSetGWorld())...I bring this up because I stumbled across this old  
post from milton aupperle on quicktime-api (june 27, 2003):

> Also, under OS 9/pre carbon , something like
>
> SGSetGWorld(gSGInfo.theSG, (CGrafPtr)gCaptureWindow, NULL);
>
> worked fine, but under Carbon, you can no longer just type cast the  
> port into the correct type, you have to specifically use the  
> correct selector type such as
>
> SGSetGWorld(gSGInfo.theSG, GetWindowPort(gCaptureWindow), NULL);
>
> to extract the correct CGrafPtr. Otherwise "interesting" things  
> happened.

...we are currently using the "bad" casting method, so maybe  
switching to the accessor will keep your "interesting" things from  
occurring?  Long shot, but then we are clawing at air...

jamie