I'm trying FreeImage, some troubles with the installation, but now it's ok. Let we see. Reading the documentation it seems simple to use..

AnotherJake Wrote:QT is not in any remote danger of being deprecated so it's hard (impossible) to recommend against using it for image loading. Unfortunately that means having to put up with DisposeGWorld for now. I would imagine they'll get this straightened out by Leopard.

The QuickTime C API is in dire danger of being deprecated, though Apple's managed not to do it formally yet. It's not available to 64-bit apps on Leopard. Neither is QuickDraw. All of QuickDraw is deprecated as of 10.4, including DisposeGWorld, despite the apparent contradiction.

GraphicsImportCreateCGImage is available from 10.3 (QT 6.4) to replace GraphicsImportSetGWorld, and ImageIO is available from 10.4 to replace the entirety of QuickTime's graphics import pipeline.

OneSadCookie Wrote:The QuickTime C API is in dire danger of being deprecated, though Apple's managed not to do it formally yet.

What!?

I'm totally shocked! I've never heard that before. What are they going to do with the Windows QT API? Obj-C?

Quote:I'm trying FreeImage, some troubles with the installation, but now it's ok. Let we see.

Look under Examples/Generic . You'll see its about 5 lines of code to load just about any image. They've made some classes too.

Initially, I was using GWorlds with Carbon. Then I switched to Quartz. Problem with Quartz was some of the calls I was using were only on os 10.4.x. Now I've gone to FreeImage in my next incarnation of stuff.

The problem with Quartz is that it assumes you want pre-multiplied alpha.

Not that this is often a major problem, though it can definitely be an issue.