apologies to all ;)

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. :)

On Fri, Jun 27, 2008 at 6:15 PM, Ken Thomases <[EMAIL PROTECTED]> wrote:

> On Jun 27, 2008, at 6:31 PM, Alex Wait wrote:
>
>  and when my program runs, the Preferences menu item is grayed out. I
>> checked
>> to make sure it was "Enabled" and it is.
>>
>> Is there some property I need to set?
>>
>
> By default, Cocoa automatically enables/disables menu items.  It does this
> based on their target and action.  If the target implements the action, then
> the menu is enabled; if not, it's disabled.  If the target is First
> Responder (i.e. nil), then Cocoa scans the responder chain for an object
> that responds to the action.  If it finds one, the menu item is enabled;
> otherwise, it's disabled.
>
> So, double-check that you've set the menu item's action.  If it's connected
> to a specific target object, make sure that object responds to that
> selector.  (Check spelling and case!)  If it's connected to First Responder,
> make sure that something in the responder chain responds.  For a Preferences
> menu, it's usually the application delegate/controller or the application
> object which would ultimately respond.  If you have an object which is
> supposed to be the application delegate, make sure it really is.  That's
> often accomplished by instantiating the delegate in the main nib and
> connecting the application's delegate outlet to it.
>
> Cheers,
> Ken
>
>


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

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 [EMAIL PROTECTED]

Reply via email to