If you do decide to use the deprecated technology, you could edit the
header and remove the macro that's just after the function declaration
so you don't get the error/warning. There are however downsides to
this. One is that your project would get an error on systems without
the modified header. Also, when you do stop using all deprecated
functions all together you might not remember you did this.
HTH,
David Alger
On Mar 25, 2007, at 1:54 PM, Mark Allen wrote:
I am writing a QuickTime based application. I have to create an
off-screen GWorld, and I use QTNewGWorldFromPtr for that. And I use
DisposeGWorld when I am done with the GWorld.
But when compiling for Tiger I get a compiler warning saying that
DisposeGWorld is deprecated. Fair enough, except I don't want
compiler warnings. I am the type of person that compilers with
warnings treated as errors.
So my question is this: 1) Is there a newer call to make other than
DisposeGWorld which is not deprecated? Other than that, is there a
way to temporarily turn off this warning around the call to
DisposeGWorld and then turn it back on on the line afterwards?
Many thanks
