• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Opening a Panel
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Opening a Panel


  • Subject: Re: Opening a Panel
  • From: "Alex Wait" <email@hidden>
  • Date: Fri, 27 Jun 2008 20:02:32 -0700

I misspelled preference.

And yeah. Xcode was telling me of my mistake. :)

On Fri, Jun 27, 2008 at 7:24 PM, Kyle Sluder <
email@hidden <email@hidden>> wrote:

> On Fri, Jun 27, 2008 at 10:01 PM, Alex Wait <email@hidden> wrote:
> > I had misspelled my action's name. I am still getting used to Obj C and
> it's
> > ability to compile methods that haven't been declared. :)
>
> You haven't specified what was misspelled (just the implementation or
> the interface declaration as well) so I'll point out the following: if
> you declare that instances of your class respond to -foo in the
> @interface block, but then in your @implementation block do not define
> -foo (through misspelling or negligence) then the compiler should warn
> you that you have an incomplete class definition.  Always heed this
> warning.  In fact, always heed all warnings.  Of course, if you didn't
> specify -foo in your class's interface, you won't get this message.
>
> If the problem was in your nib, IB may be able to warn you that you
> specified an incorrect action.  If you directly connect a view to a
> target and specify an action that the object doesn't claim to respond
> to (again, misspelling or neglecting to type the action as IBAction
> are the most common culprits) then IB will throw up a warning.  But if
> you connect the view to First Responder, IB has no idea what objects
> are in the responder chain and can't provide this helpful warning.
>
> The point I'm trying to make is to always heed warnings and fix them.
> As a beginner, in particular, you should probably turn on "Treat
> Warnings as Errors" in your target settings, so that you can't ignore
> compiler warnings.
>
> --Kyle Sluder
>



--
If you can't be kind, at least have the decency to be vague.
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

References: 
 >Opening a Panel (From: "Alex Wait" <email@hidden>)
 >Re: Opening a Panel (From: Ken Thomases <email@hidden>)
 >Re: Opening a Panel (From: "Alex Wait" <email@hidden>)
 >Re: Opening a Panel (From: "Kyle Sluder" <email@hidden>)

  • Prev by Date: Re: Core data question in multiwindow doc app
  • Next by Date: Re: NSString uppercaseString
  • Previous by thread: Re: Opening a Panel
  • Next by thread: How can I find the source of random crashes when using debug frameworks
  • Index(es):
    • Date
    • Thread