THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 06/09/2008 at 11:56, xxxxxxxx wrote:
Cinema 4D Version: R11
Platform: Mac OSX ;
Language(s) : C++ ;
What exactly do I do about this? I'm using the Carbon.Framework for all sorts of Mac file/resource access (required) but all I'm getting are thousands and thousands of 'deprecated' warnings. Can I just suppress the warnings and pray?
Will using the MacOSX10.4u.sdk framework cause problems running the 64-bit version of Cinema 4D on 10.5?
On 06/09/2008 at 12:47, xxxxxxxx wrote:
Praying didn't help. The Carbon.Framework isn't 64-bit compatible. Any suggestions on porting Carbon code to Cocoa code using the Cocoa.Framework instead?
On 08/09/2008 at 01:47, xxxxxxxx wrote:
I saw you had also a discussion about this with per on CGtalk. Did this help you because to be honest I am not that familiar with the inner workings of Carbon or Cocoa.
On 08/09/2008 at 07:29, xxxxxxxx wrote:
Neither am I.
Not that far into the port process yet. I figure that what I can do in MacOS C4D R11 is:
1. Dump system-dependent Carbon code altogether. This will break support for MacOS Resources to get thumbnail PICT images, but people will have to live with it. Resources were made deprecated by Bundles long ago. Poser and Daz should get the hint.
2. Use GeGetStartupWritePath() to get the 'writable' directory instead of Carbon or Cocoa methodologies.
3. Maybe switch over to CompressData()/UncompressData() for zlib support - this may not be required but we'll see.
4. Dump libpng if it is not Mac 64-bit compatible. This one hurts as it allows much faster load of PNG thumbnail files (compared to QuickTime) and has better results (compared to QTs odd alpha handling these days). There are really no alternatives.