Roland, Yes, I just discovered that I was creating the object template from the Mac OS X section even though I created the project from iOS. Now, I have no idea how that template section got referenced but it seems to be that the template selection should be automatically switched to iOS if you create the project from iOS. I will have to watch that in the future.
phil On Jan 3, 2011, at 8:23 PM, Roland King wrote: > Which template are you using to add the object ... > > There's two sets, the ones at the top of the list are for iOS, the ones at > the bottom are for OS X, you want to add an object from the top set. > > On 04-Jan-2011, at 12:20 PM, Phil Hystad wrote: > >> I just did it again. I create a new project, iOS View Application for iPad. >> Do an immediate build and it works and runs fine (with blank view of >> course). The, I add a class, which I called MyModel just for the heck of >> it. It is based on NSObject and it imports Cocoa.h as generated by the >> template. Now, when I build, it gets an error because Cocoa.h is not found. >> >> There must be some problem with my template. I am up to date on Xcode and >> the SDKs and I think I refreshed the iOS SDKs just the other day. So, >> either I have something screwed up in my templates (which I have never >> mucked with) or there is a bug in the template as it came from Apple. >> >> phil >> phys...@mac.com >> >> >> On Jan 3, 2011, at 8:11 PM, Roland King wrote: >> >>> ipad? That's iOS and those templated files should include >>> <Foundation/Foundation.h> not <Cocoa/Cocoa.h>, did you pick the wrong file >>> type from the template. >>> >>> On 04-Jan-2011, at 1:47 AM, Phil Hystad wrote: >>> >>>> I just started playing around with Xcode and Cocoa again and doing a few >>>> little iPad apps. When I add a class to the project, (simple NSObject >>>> based class) the .h file includes the import for <Cocoa/Cocoa.h>. But, >>>> the build and compile fails because it says this header file is not found. >>>> >>>> This happens even if I do absolutely nothing to the class files other then >>>> use the regular File create class option. This can be repeated easily by >>>> merely creating an iPad view application shell. If you do an immediate >>>> build it works. If you were to create a new class as I described (and not >>>> modify the generated .h,.m files) the build fails with the Cocoa.h file >>>> not being found. >>>> >>>> Obviously something is askew in what I am doing. >>>> >>>> phil >>>> phys...@mac.com >>>> >>>> _______________________________________________ >>>> >>>> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) >>>> >>>> Please do not post admin requests or moderator comments to the list. >>>> Contact the moderators at cocoa-dev-admins(at)lists.apple.com >>>> >>>> Help/Unsubscribe/Update your Subscription: >>>> http://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org >>>> >>>> This email sent to r...@rols.org >>> >> > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
