[ddregs]

Hi all,
after a 6 years hiatus with CodeWarrior C Mac software development, I recently decided to restart all over again and begin studying Carbon, which is the simplest way to put my hands on OS X to me.
I am building a simple application to do some image manipulations, and I have some problems with the infamous PICT rsrc files. I created an image for the About Box, I saved it w/Photoshop as a PICT resource file, I added it to the XCode project, and I can see it in Interface Builder. I added it to the dialog, and if I do the Test Interface (Interface Builder command) it all works and I can see the image.
But when I build the application and run it, I don't see any image at all. I cleaned all the targets, I checked the content of the application (Show Package Contents), I can see the .rsrc file but it's 0 bytes.
Anyone can help me out? Thanks in advance!
(I followed every single word from Learning Carbon book btw)

[larkost]

Did you make sure that the pict is included in the target you are building?

And why Carbon... if you are learning to write Mac Programs again (and by getting into Carbon after 6 years you are) why are you not using the recommended environment for new programs: Cocoa? Carbon is only recommended when you have legacy code that you have to bring in... and even that has been heavily reduced by ObjC++. Now the only reasons are:

You have to have a functional (as opposed to Object-Based) interface because you are also compiling for Windows.

You have a large existing MacOS 8/9 codebase that you want to keep using. And then you are more likely to stick with CodeWarrier as I am told the XCode import routine still has kinks.

[ddregs]

Originally Posted by larkost

Did you make sure that the pict is included in the target you are building?

And why Carbon... if you are learning to write Mac Programs again (and by getting into Carbon after 6 years you are) why are you not using the recommended environment for new programs: Cocoa? Carbon is only recommended when you have legacy code that you have to bring in... and even that has been heavily reduced by ObjC++. Now the only reasons are:

You have to have a functional (as opposed to Object-Based) interface because you are also compiling for Windows.

You have a large existing MacOS 8/9 codebase that you want to keep using. And then you are more likely to stick with CodeWarrier as I am told the XCode import routine still has kinks.

Hi Larkost,
I wanted to thank you for the suggestion for a long time now, but I couldn't since I was locked out by a change of mail address profile here which didn't send the activation until now. I wrote to the admin@macnn.com mailbox without any luck unfortunately.

In the meantime, I listened and practiced your suggestion. I bought 2 Cocoa books, one is the Learning Cocoa with Objective-C O'Reilly Book and the other is Cocoa Programming 2nd edition by Aaron Hillegass. 2 great books.

And what a wonderful environment Cocoa is! I know what I was missing only now. I'm back into full Mac-programming mode tks to Cocoa.

Cheers!