Apple

On Feb 20, 2009, at 8:35 AM, john smith wrote:

Then I need some way for that view to communicate with my C++ code. Then that C++ code need to communicate with some other cocoa code, because drawing functions no longer are support in carbon.

I'm unclear on what you mean here. If you mean Quickdraw, that technology has been barely supported for most of Mac OS X, and formally deprecated in 10.4. You should be using Core Graphics (aka Quartz) which is fully supported in both the Carbon and Cocoa environments.

-> Currently I'm using CopyBits. I don't know if that is Quickdraw or Quartz.

When your ready to draw your buffer, wrap it in a CGImageRef, draw the image and release the image again.

-> Sounds like a good pointer, thanks. Can I do that from inside C++ code? Also on 64-bit OS's?

Do you see what I mean? There's absolutely no gain for me in cocoa, only extra work. Nothing of what I do on a daily basis uses the OS calls, so it doesn't matter if they're a hassle... If they are an obstacle, then they're an obstacle that I've already crossed..

If you've been following Apple's recommendations for event handling and graphics, then you are already 90% of the way there.

-> I beg to differ.

Carbon Events for event handling mirror into the event system in Cocoa fairly well (except you don't have to install event handlers, you just override methods). Graphics should be using Quartz, which is available to both Carbon & Cocoa applications for drawing. File handling and a lot of other non-GUI stuff doesn't need to change at all.

-> Sorry, I'm somewhat confused here... People tell me that carbon drawing is not supported in the 64-bit version of the OS... But it sounds to me like I can use Quartz still, also from C++ (actually I asked that above also)

If your not using Quartz, then your graphics work will be harder. If your not using Carbon Events, then your event work will be harder. But neither of these have been the recommended methods either.

-> Well, moving to Quartz shouldn't be too much work, though, as long as I don't have to mess around with obj-c. I am using carbon events.

Thanks,

Michael Olsen

References:
	>Audio unit hosting (From: James Membrez <email@hidden>)
	>Re: Audio unit hosting (From: William Stewart <email@hidden>)
	>Cocoa and future (From: john smith <email@hidden>)
	>Re: Cocoa and future (From: tahome izwah <email@hidden>)
	>FW: Cocoa and future (From: john smith <email@hidden>)
	>Re: Cocoa and future (From: Jens Alfke <email@hidden>)
	>RE: Cocoa and future (From: john smith <email@hidden>)
	>Re: Cocoa and future (From: David Duncan <email@hidden>)